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.

Quickstart

Connect an agent in one step

REQO speaks the Model Context Protocol over Streamable HTTP. Point your client at the endpoint and it discovers the rest.

{
  "mcpServers": {
    "reqo": {
      "type": "streamable-http",
      "url": "https://reqo.me/mcp"
    }
  }
}

initialize and tools/list work without authentication, so a client can discover the surface before anyone signs in. Full walkthrough in the MCP skill.

Tools

What an agent can call

Generated from the server's own tool registry, so this list is the list.

ToolAuthWhat it does
health_checkNoneHealth check
list_videosSessionList videos
get_videoSessionGet a video
get_captionsSessionGet captions or subtitles
list_projectsSessionList editing projects
create_projectSessionCreate an editing project
transcribe_videoSessionTranscribe REQO-hosted media
Reference

Every machine-readable document

All live, all at predictable URLs.

OpenAPI 3.1 spec

/openapi.json

Every externally drivable endpoint, typed, with an operationId on each.

MCP server

/mcp

Streamable HTTP. The same surface as tools an agent can call directly.

MCP server card

/.well-known/mcp/server-card.json

Generated from the tool registry, so it cannot advertise a tool that does not exist.

Authentication

/auth.md

How an automated client authenticates. Includes a machine-readable agent_auth block.

Agent skills index

/.well-known/agent-skills/index.json

Task-shaped guides with sha256 digests computed from the files.

API catalog (RFC 9727)

/.well-known/api-catalog

Linkset pointing at every service description.

Scoped LLM index

/api/llms.txt

The programmatic surface only, without the marketing sections.

Machine-readable pricing

/pricing.md

Plans and limits, generated from the same source the pricing page renders from.

Payment discovery

/.well-known/ucp

What can be paid for per call, and how.

Agent view of the homepage

/?mode=agent

Capabilities, auth and endpoints as JSON instead of marketing HTML.

Authentication

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.

Payments

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.

Agent payments are not currently enabled on this deployment: these endpoints return 503 until a receiving wallet is configured.

Start with the spec.

Free to use, no credit card, no key to request. Questions go to a human.