Try it live. The API playground takes your key, sends the request and shows the real answer — the status, the timings, the headers and the body — with the curl, Python and JavaScript snippets built from what you fill in. The machine-readable reference is api.md.

The endpoints

A request in five lines

The whole API is one multipart POST for the file. Everything else reads the result back.

curl -X POST "https://api.transcrib.si/v1/transcripts" \
  -H "X-API-Key: $TRANSCRIB_API_KEY" \
  -F "file=@meeting.mp3" \
  -F "language=auto" \
  -F "diarize=true"

And the same call from Python:

import httpx

with open("meeting.mp3", "rb") as audio:
    response = httpx.post(
        "https://api.transcrib.si/v1/transcripts",
        headers={"X-API-Key": API_KEY},
        files={"file": ("meeting.mp3", audio, "audio/mpeg")},
        data={"language": "auto", "diarize": "true"},
        timeout=120.0,
    )

transcript_id = response.json()["id"]  # status: queued

The answer comes back as {"id": …, "status": "queued"}. The transcript is not ready yet: read it with GET /v1/transcripts/{id} until the status is done. The segments come in the same answer, each with start_s, end_s, the text and the speaker.

The errors

Every endpoint answers with the same shape, so one handler covers the whole API: {"error": {"code": "…", "message": "…"}}.

The limits

What the API costs

API usage is metered and billed by volume, separately from any subscription: there is no API plan with a monthly fee attached to it. We do not publish a per-hour rate — write to us with your monthly volume and we will send the rate for it.

The MCP server and the plugins

The same host serves an MCP server at /mcp with four tools — transcribe_audio, summarize_transcript, extract_actions and list_transcripts — and the plugins for Claude and ChatGPT use it. The details, the OAuth flow and the tool schemas are on the page for developers and agents. The page Transcrib in ChatGPT and Claude tells you what works with the two assistants today, what is still missing and how to connect the server yourself.

The keys

An API key is created in the app and its value is shown exactly once; we store only its hash. Send it in the X-API-Key header, or send a session token as Authorization: Bearer …. A key can be revoked from the app at any moment, and a revoked key stops working immediately.

The browser extension uses the same two ways to authenticate: paste the API key or the access token into its settings, and it is sent in the same headers.