Changelog

Non-breaking additions (new optional fields, new endpoints, new format params, new error types) ship on v1 without notice. Breaking changes ship under /api/v2/*.

v1

2026-09-10: documentation refresh

Reference coverage for capabilities already available in v1 and the website:

• YouTube and channel search, video info, and channel playlists and counts.
• GET /jobs, cross-surface job kinds, comments counters, skipped videos, and standalone comments exports.
• Website comments collections: per-video amounts, replies, a credit budget, background processing, and JSON/CSV ZIP downloads.
• Clarified metadata availability, shared-credit reservations, sync retry charges, and the difference between REST and MCP channel-job submission.

2026-09-07

• Bulk jobs optionally include one Top comments page per successful transcript. Website, API, and MCP reserve up to 2 credits per video and refund unused credits. Comments are saved with the job, included as JSON files in its ZIP, and free to read back.
• API and MCP comments now cost 1 shared credit per nonempty page, including continuation and reply pages. Errors and empty pages are not charged; at least 1 available credit is required to fetch.
• MCP get_transcript with include_comments costs 2 credits when both succeed. A comments failure does not discard or add a charge to a successful transcript.
• Plan prices and credit allowances are unchanged. Existing transcripts_* usage fields now count shared credits; their names and response shapes are unchanged. Search and video details remain free. The workbench also offers optional comments, charged at 1 credit per nonempty page.

2026-09-05

• The MCP authorization server accepts OAuth Client ID Metadata Documents. Claude’s Use Anthropic’s hosted client metadata option now works. Dynamic Client Registration remains supported.

2026-05-21

• v1 launched. Eight endpoints across sync transcripts, bulk jobs, resolve, and usage.
• Stable error envelope: { error: { type, message, details? }, request_id }.
• Bearer token authentication with one active key per account.
• Per-plan rate limits and shared monthly quota across web and API.
• Idempotency-Key support on POST /jobs.