API Overview

rtrvr.ai exposes three HTTP endpoints for different automation needs: full agent runs, raw page scraping, and browser-as-API for your logged-in Chrome. All share the same authentication and credit system.

Try Playground Get API Key Install Extension

Three Endpoints

POST/agent

Agent API

Full planner + tools engine for end-to-end web automations.

POST/scrape

Scrape API

Accessibility tree as context for your own agent.

POST/mcp

Browser as API/MCP

Control your logged-in Chrome via HTTP or MCP.

Authentication

All endpoints use the same API key. Pass it via the Authorization header:

Header

Authorization: Bearer rtrvr_your_api_key

MCP OAuth Support

For /mcp, clients with OAuth can connect to mcp.rtrvr.ai directly for Google Sign-In authentication.

Security

Keep your key server-side. Never embed it in browser code or ship it to clients.

Unified Playground

API Playground

POST /agent

Full planner + tools engine for end-to-end web automations.Full docs →

API Key

Get your API key from rtrvr.ai/cloud

Task Description*

Starting URLs

Response Verbosity

Output Schema (JSON)

curl -X POST "https://api.rtrvr.ai/agent" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "input": "",
  "urls": [
    "https://news.ycombinator.com/"
  ],
  "response": {
    "verbosity": "final"
  }
}'

When to Use What

Use Case	Endpoint	Why
End-to-end web automation	`/agent`	Full planner + tools, can write to Sheets/Docs
Feed your own LLM/RAG pipeline	`/scrape`	Infra-only credits, returns raw text + tree
Use logged-in sessions (Gmail, Salesforce)	`/mcp`	Runs in your Chrome via extension
Bulk data extraction	`/agent`	Use dataInputs + sheets_workflow
Quick page content check	`/scrape`	Cheapest option, predictable schema
MCP client integration (Claude, etc.)	`/mcp`	Direct MCP protocol support

/agent

• Model + infra credits
• Higher latency (LLM calls)
• Full automation capability

/scrape

• Infra-only credits
• Lower latency
• Raw data for your models

/mcp

• Your logged-in browser
• MCP + HTTP + OAuth
• Access authenticated sites

New: File & Image Inputs

All agent and MCP credit tools now support file and image inputs via publicly fetchable URLs:

file_urls

CSV, PDF, text files to use as input data for workflows

image_urls

JPG, PNG images for visual context and recognition

recording_id

Use a recorded workflow as context for replay

Example: Agent API with file inputs

{
  "input": "Upload this CSV and submit the form",
  "urls": ["https://example.com/upload"],
  "file_urls": ["https://example.com/data.csv"],
  "image_urls": ["https://example.com/screenshot.png"],
  "recording_id": "rec_abc123",
  "response": { "verbosity": "final" }
}

Ready to automate?

Join teams using rtrvr.ai to build playful, powerful web automation workflows.