Choose a plan or volume
Pick a public plan, or tell us the monthly transcript quota and rate limit you expect.
Choose a Scority plan for YouTube transcript extraction, JSON responses, language options, rate limits and fallback processing for harder videos.
Scority plans are priced around monthly transcript quota. API keys work from trusted server-side code with x-api-key, and responses include transcript text, timestamped segments, source and language.
Scority uses contact-based onboarding today. The request confirms quota, rate limit and server-side key setup before production traffic starts.
Pick a public plan, or tell us the monthly transcript quota and rate limit you expect.
Use the access form or contact page with your use case, languages and expected traffic.
We confirm the account quota, request pattern and whether fallback review is relevant.
Your API key is issued for trusted server-side code. Do not expose it in browser JavaScript.
Use /docs/api or the OpenAPI spec to call GET /v1/youtube/transcript.
Pick the request volume you expect this month. If the workload is spiky, customer-facing, or needs account-specific fallback routing, start with Pro, Scale, or Enterprise.
For prototypes and small automations
For apps, RAG pipelines and internal tools
For production workflows
For high-volume transcript workflows
Custom pricing for accounts that need custom quota, custom rate limits, fallback processing terms, or operating support beyond the public plans.
Talk to Scority →Included quota covers the monthly transcript volume in your plan. Extra usage lets a real product keep running when traffic goes above the included amount, without forcing a plan migration mid-month.
Monthly quota controls account-level transcript volume. Rate limits control short-window pressure so the API remains usable for production clients.
Scority first uses accessible caption tracks. For harder videos and supported accounts, the infrastructure can route work through proxy/captcha handling and GPU-capable fallback processing. This improves the operating range without pretending every video is guaranteed.
The pricing model is designed for developers who mainly need transcripts, not a broad social data platform. Compare providers by included monthly transcripts, extra usage, rate limits, language behavior, support needs and actual response shape.
Scority focuses on the transcript endpoint and JSON shape that AI apps need.
Open →Use x-api-key from trusted server-side code. Do not expose API keys in frontend JavaScript.
Open →Handle transcript_not_available, upstream_transcript_failed, rate_limited and quota_exceeded explicitly.
Open →These answers cover billing shape, request counting and fallback expectations without claiming self-serve checkout is live.
A transcript request is a call to GET /v1/youtube/transcript. Successful transcript responses count toward the monthly transcript quota. Invalid input and unauthorized calls should be fixed by the client instead of retried.
Fresh fetches may need upstream caption work. Cached requests can return faster for the same video and language bucket. Both still use the API and should be counted as transcript workload.
Extra usage is billed by the plan's per-1,000 transcript rate or handled by an agreed custom quota. Contact Scority before a scheduled traffic spike so limits can be sized correctly.
No. Monthly quota controls account-level transcript volume. Rate limits control short-window request pressure and return Retry-After plus X-RateLimit headers.
No. Scority has fallback infrastructure for harder videos, including proxy/captcha routing and GPU-capable processing capacity for supported accounts, but no transcript service should promise every-video coverage.
Use Get API access or Contact us with your plan choice, use case and expected monthly volume. Scority confirms quota and rate limit, then issues a server-side API key for your account.
Share your expected monthly transcript volume, target languages and whether the workload is internal or customer-facing. Scority will issue access through the current manual onboarding flow.
Request a plan and describe the application you are building.
Open →Use contact when your workload includes harder videos, high volume or custom support needs.
Open →Review parameters, response fields, errors and rate-limit headers before integrating.
Open →