Agents

YT2Text is usable from AI agents today through the public REST API at

https://api.yt2text.cc/api/v1

The public onboarding files are:

```
https://yt2text.cc/skill.md
```
```
https://yt2text.cc/skill.json
```
```
https://yt2text.cc/skill.jsonl
```
```
https://yt2text.cc/agents
```

Who this is for

This guide is for agent systems that can:

read Markdown instructions
store API keys securely
make authenticated HTTPS requests
poll asynchronous jobs and fetch results later

That includes common agent/operator environments such as:

Codex
GPT-based agents
Claude
Claude Code
OpenClaw
Hermes agents
internal orchestration agents

Human setup

Before an agent can call the API, a human must:

Create an account at
```
https://yt2text.cc/auth/signup
```
Choose a plan at
```
https://yt2text.cc/pricing
```
Open
```
https://yt2text.cc/dashboard/api-keys
```
Create an API key and copy it immediately

Plan gates:

```
free
```
: no API keys,
```
tldr
```
only
```
plus
```
: API keys enabled, all summary modes
```
pro
```
: batch processing, webhooks, custom prompts, PDF export, infographics, AI chat, priority queue

If the goal is external agent usage,

plus

is the minimum plan.

API-first workflow

Recommended flow:

Read
```
https://yt2text.cc/skill.md
```
Store the key in an environment variable such as
```
YT2TEXT_API_KEY
```
Submit a video with
```
POST /api/v1/videos/process
```
Poll
```
GET /api/v1/videos/status/{job_id}
```
Fetch
```
GET /api/v1/videos/result/{job_id}
```

Authentication

Preferred header:

Authorization: Bearer <api_key>

Also supported:

X-API-Key: <api_key>

Query parameter authentication is not supported.

Example request

curl -X POST https://api.yt2text.cc/api/v1/videos/process \
  -H "Authorization: Bearer $YT2TEXT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
    "options": {
      "summary_modes": ["tldr", "detailed"],
      "language": "en"
    },
    "service_name": "agent-platform",
    "agent_name": "research-agent",
    "client_reference": "job-123"
  }'

Agent-specific guidance

Prefer async processing, not synchronous assumptions
Keep keys server-side only
Use
```
service_name
```
,
```
agent_name
```
, and
```
client_reference
```
for correlation
Treat
```
/api/v1/usage/*
```
as diagnostic today, not billing truth
Back off on
```
429
```
responses using
```
Retry-After
```

Public documentation

What comes next

The sequence for YT2Text agent support is:

REST API and public skill files
first-party SDKs
MCP after the API and SDK contract is hardened

See Agents roadmap.