Fast Transcriber Docs

Build transcription into your workflow

Queue audio, video, and public links through the REST API, or let an AI assistant use Fast Transcriber through Model Context Protocol.

API and MCP jobs use the same processing pipeline, plan access, file limits, and saved transcript history as the web application.

Quickstart

Sign in and create an API key from the developer section.
Store the key in an environment variable, never in source code.
Queue a URL and poll the returned job until it completes.

bash

curl --request POST https://fast-transcriber.com/api/v1/transcriptions \
  --header "Authorization: Bearer $FAST_TRANSCRIBER_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "source_url": "https://www.youtube.com/watch?v=example",
    "speaker_diarization": false
  }'

Authentication

Protected REST and MCP requests use the same bearer key. Production keys begin with ft_live_ and can be revoked at any time.

http

Authorization: Bearer ft_live_replace_me

Choose an integration

REST API

For applications, backend services, and direct upload flows.

Read the API guide

MCP server

For AI assistants that should queue and retrieve transcripts.

Set up MCP

Account limits

Developer requests count toward the authenticated account's normal usage. Free accounts receive the same preview behavior as the browser, while speaker diarization requires Pro.