API-first for agents
Give agents a real YouTube-to-text workflow today, then layer SDKs and MCP on top.
YT2Text is already usable from agents over the public REST API and the live remote MCP server. The live path today is account → plan → API key → REST or MCP → transcript workflows. This page is the human-facing entry point for agent setup.
Quick start
Read https://yt2text.cc/skill.md Use https://api.yt2text.cc/api/v1 MCP https://mcp.yt2text.cc/mcp Auth: Authorization: Bearer sk_... Plan: Plus or Pro for API access Minimum plan for agent API usage: Plus
Batch, webhooks, PDF export, custom prompts: Pro
How agent access works
The live integration path is intentionally simple: use REST when you want direct HTTP control, or use MCP when your client can discover and call tools.
Step
Provision access
Create an account, choose Plus or Pro, and generate an API key in the dashboard. API access starts at Plus.
Step
Choose REST or MCP
Use the public REST API directly, or connect the live remote MCP server at https://mcp.yt2text.cc/mcp.
Step
Run async jobs
Submit a video, poll status, fetch results, or let the MCP tool summarize and return Markdown for the agent.
Compatibility
Built for agents that can fetch Markdown, call HTTPS APIs, or connect to MCP
This is the compatibility layer you want first. If an agent runtime can read `skill.md`, keep secrets, make authenticated HTTP calls, or call remote MCP tools, it can use YT2Text today.
Codex
GPT-based agents
Claude
Claude Code
OpenClaw
Hermes agents
custom internal agent runtimes
Operational instructions
The exact workflow an agent should follow
This mirrors the public skill and keeps the first version API-native. No separate package is required to get started.
- 1
Read
https://yt2text.cc/skill.md - 2
Store
YT2TEXT_API_KEY server-side - 3
POST
/api/v1/videos/process - 4
Poll
/api/v1/videos/status/{job_id} - 5
Fetch
/api/v1/videos/result/{job_id} - 6
Upgrade
Use Pro for batch, webhooks, and PDF export
Current platform status
What exists now vs. what is planned
| Capability | Status | Notes |
|---|---|---|
| Public REST API | Live now | Single-video async processing with transcript and summary payloads. |
| Agent skill file | Live now | Public `skill.md` and `skill.json` on the root domain for agent onboarding. |
| API keys | Live now | Created in the dashboard. Minimum plan: Plus. |
| MCP server | Live now | Remote Streamable HTTP MCP server at `https://mcp.yt2text.cc/mcp` with five YT2Text tools. |
| Batch processing | Pro | Available today via `/api/v1/batch/*` for high-volume workflows. |
| Webhooks | Pro | Single-job completion callbacks are live. Batch completion delivery still needs product work. |
| First-party SDKs | Planned | JavaScript/TypeScript and Python first, then Swift and Kotlin. |
Roadmap
The next steps after API and MCP launch
We should not block agent adoption on the perfect package story. REST and MCP are live now; SDKs and platform hardening come next.
Phase 1
API and MCP onboarding
Keep REST, skill files, and the MCP server documented clearly so agents can integrate today without waiting for SDKs.
Phase 2
Official SDKs
Wrap auth, polling, retries, and typed responses into first-party packages so agents stop rewriting the same client logic.
Phase 3
Platform hardening
Tighten webhook signing, idempotency guidance, batch completion events, and usage diagnostics around the live tool layer.
Start now
Agents can integrate today over REST or MCP.
Create an account, generate a key, hand the agent the public skill, or connect the MCP server with the same API key.