RAG and AI agents
Feed clean, timestamped transcripts into embeddings, vector databases and LLM pipelines without scraping captions yourself.
One REST API for structured transcripts from public YouTube videos, playlists and channels. Predictable credits, machine-readable output, and clear errors. Free to start.
# quickstart.sh curl "https://api.example.com/v1/transcripts/VIDEO_ID" \ -H "Authorization: Bearer YOUR_API_KEY"
{
"video_id": "dQw4w9WgXcQ",
"language": "en",
"duration": 213,
"segments": [
{ "text": "...", "start": 18.64, "duration": 3.24 }
]
}
Ask for the format you already use. Responses are stable and timestamped, so downstream tools never guess.
Single video, batch up to 50, playlists and channels. JSON, TXT, SRT, VTT, Markdown.
Large requests become asynchronous jobs with per-item status, retries and webhooks.
Grounded answers with timestamps, summaries and chapters. Small and focused at launch.
Feed clean, timestamped transcripts into embeddings, vector databases and LLM pipelines without scraping captions yourself.
Pull transcripts for a playlist or an entire channel in one job, then analyse themes, sentiment or speaking time.
Export SRT, VTT or plain text to publish subtitles, build an accessible archive, or repurpose video into articles.
Wire transcripts into MCP servers, Claude Code and Codex so your agents can read any video on demand.
Limits are configuration-driven and may change as the API stabilises.
Authorization: Bearer YOUR_API_KEY
# or
X-API-Key: YOUR_API_KEY
Keys are hashed at rest, shown once, revocable, and scoped per account.
{
"error": {
"code": "TRANSCRIPT_NOT_AVAILABLE",
"message": "...",
"request_id": "req_123"
}
}
Every request carries an X-Request-ID for support and debugging.
The canonical schema is published and importable into Postman and other tooling.
Yes. Every account gets 10,000 free credits and a developer key — no credit card required. Single-video requests cost one credit each, so you can build and test without paying.
Call GET /v1/transcripts/{videoId} with your key in the Authorization header. You get the transcript, its language, duration and timestamped segments as JSON.
Yes. List a video’s caption tracks with GET /v1/transcripts/{videoId}/languages, then pass ?lang= to fetch the one you want. Automatic captions are labelled so you know their quality.
JSON, TXT, SRT, VTT and Markdown. Use ?format= on transcript requests, or convert the JSON yourself — the segments are plain text plus start and duration.
Yes. A few lines with requests or httpx are enough — see the blog guide for a copy-paste Python quickstart, including batching and retries.
Yes. Batch up to 50 video IDs with POST /v1/transcripts, or start a playlist or channel job that returns one result per video with per-item status.
Yes. An MCP server exposes transcript tools to Claude Code, Codex and other MCP clients, so an agent can pull a video’s transcript without bespoke glue code.
The API is free while in early access: 10,000 credits per account and 60 requests/minute. Paid plans with higher limits are coming soon.
Create a free developer key, make your first request in a minute, and ship transcripts your users can actually search, quote and export.