Build on REQO.
Recording, transcript-based editing, captions and cloud export, available to your code and to your agents. There are no API keys to request and no sales call: you sign in, and your session is the credential.
Connect an agent in one step
REQO speaks the Model Context Protocol over Streamable HTTP. Point your client at the endpoints and it discovers the rest: the product server acts on your workspace, the documentation server answers questions with no sign-in.
{
"mcpServers": {
"reqo": {
"type": "streamable-http",
"url": "https://reqo.me/mcp"
},
"reqo-docs": {
"type": "streamable-http",
"url": "https://reqo.me/mcp/docs"
}
}
}initialize and tools/list work without authentication, so a client can discover the surface before anyone signs in. Full walkthrough in the MCP skill.
What an agent can call
Generated from the server's own tool registry, so this list is the list.
| Tool | Auth | What it does |
|---|---|---|
| health_check | None | Health check |
| list_videos | Session | List videos |
| get_video | Session | Get a video |
| get_captions | Session | Get captions or subtitles |
| list_projects | Session | List editing projects |
| create_project | Session | Create an editing project |
| transcribe_video | Session | Transcribe REQO-hosted media |
| show_plans | None | Show REQO plans |
Every machine-readable document
All live, all at predictable URLs.
/openapi.json
Every externally drivable endpoint, typed, with an operationId on each.
/mcp
Streamable HTTP, JSON-RPC 2.0 over POST. The same surface as tools an agent can call directly.
/mcp/docs
Read-only and needs no auth: search_docs and get_doc over every published guide, tool page and reference.
/.well-known/mcp/server-card.json
Generated from the tool registry, so it cannot advertise a tool that does not exist.
/auth.md
How an automated client authenticates. Includes a machine-readable agent_auth block.
/.well-known/agent-skills/index.json
Task-shaped guides with sha256 digests computed from the files.
/pricing.md
Plans and limits, generated from the same source the pricing page renders from.
/?mode=agent
Capabilities, auth and endpoints as JSON instead of marketing HTML.
No API keys, by design
REQO authenticates a human and an agent acts on their behalf.
Send the user through the interactive sign-in at /api/auth/signin, then forward the resulting session cookie on every request. Confirm it at any time with GET /api/auth/session, which returns the user or {}.
A 401 means the cookie is missing or expired: sign in again rather than retrying. A 403 means the session is valid but the resource is deliberately gated.
Responses carry the standard RateLimit headers (RFC 9331) plus Retry-After on a 429, so you can self-throttle instead of guessing.
Pay per call, no account
Some endpoints can be bought outright over x402, for agents with no REQO login.
POST /api/agent/transcribe
Transcribe audio or video from a public HTTPS URL with Whisper large-v3. Pay per call, no account required.
$0.05 (0.05 USDC) per request
Call without an X-PAYMENT header to receive a 402 describing exactly what to pay. Payment is verified before the work runs and settled only once it succeeds, so a failed call is not charged.
Start with the spec.
Free to use, no credit card, no key to request. Questions go to a human.