Scority

YouTube Transcript API Pricing

Choose a Scority plan for YouTube transcript extraction, JSON responses, language options, rate limits and fallback processing for harder videos.

Clear quota-based access for transcript workloads.

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.

  • Use video_id or video_url, plus optional language or lang.
  • Rate limits and monthly quota are separate controls.
  • Successful transcript responses count toward quota.
  • Harder videos can be reviewed for supported fallback processing.

How API access works

Scority uses contact-based onboarding today. The request confirms quota, rate limit and server-side key setup before production traffic starts.

Step 1

Choose a plan or volume

Pick a public plan, or tell us the monthly transcript quota and rate limit you expect.

Step 2

Send an access request

Use the access form or contact page with your use case, languages and expected traffic.

Step 3

Confirm quota and fit

We confirm the account quota, request pattern and whether fallback review is relevant.

Step 4

Receive a server-side key

Your API key is issued for trusted server-side code. Do not expose it in browser JavaScript.

Step 5

Start from the API docs

Use /docs/api or the OpenAPI spec to call GET /v1/youtube/transcript.

Plans

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.

Starter

For prototypes and small automations

$9/mo
Included
2,000 transcripts / month
Extra usage
$2 per 1,000 extra
Rate limit
10 rpm
  • Server-side x-api-key access
  • JSON transcript response
  • Timestamped segments
  • Language parameter support
Request Starter

Builder

For apps, RAG pipelines and internal tools

$19/mo
Included
10,000 transcripts / month
Extra usage
$2 per 1,000 extra
Rate limit
30 rpm
  • Higher monthly quota
  • Language-aware cache behavior
  • Rate-limit headers
  • Normalized transcript errors
Request Builder

Pro

For production workflows

$49/mo
Included
50,000 transcripts / month
Extra usage
$1 per 1,000 extra
Rate limit
60 rpm
  • Production quota planning
  • Fallback review for harder videos
  • Usage and quota support
  • Integration guidance
Request Pro

Scale

For high-volume transcript workflows

$149/mo
Included
250,000 transcripts / month
Extra usage
$0.70 per 1,000 extra
Rate limit
120 rpm
  • High-volume request quota
  • Proxy/captcha routing review
  • GPU-capable fallback capacity
  • Priority operating support
Request Scale

Enterprise

Custom pricing for accounts that need custom quota, custom rate limits, fallback processing terms, or operating support beyond the public plans.

Talk to Scority →
  • Custom monthly quota
  • Custom rate limit
  • Fallback processing by agreement
  • Proxy/captcha routing by agreement
  • Support and SLA terms by agreement

Included quota and extra usage

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.

Starter and Builder

$2 per 1,000 extra transcripts for early products and internal tools.

Open →

Pro

$1 per 1,000 extra transcripts for production workflows with steadier volume.

Open →

Scale

$0.70 per 1,000 extra transcripts for high-volume accounts.

Open →

Rate limits and monthly quota are different.

Monthly quota controls account-level transcript volume. Rate limits control short-window pressure so the API remains usable for production clients.

  • rate_limited is a short-window protection response. Respect Retry-After before retrying.
  • quota_exceeded means the monthly transcript quota is exhausted or needs adjustment.
  • X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset help clients back off cleanly.
  • High-volume jobs should be sized before they run.

Fallback processing for harder videos

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.

  • Caption tracks remain the fastest path when YouTube exposes usable captions.
  • Proxy/captcha routing is used as an engineering control for difficult upstream access, not as a blanket public promise.
  • GPU-capable fallback capacity is available for account-specific processing paths.
  • The API still returns transcript_not_available or upstream_transcript_failed when a transcript cannot be retrieved safely.

Competitive for transcript-heavy workloads

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.

Transcript-specific

Scority focuses on the transcript endpoint and JSON shape that AI apps need.

Open →

No browser key pattern

Use x-api-key from trusted server-side code. Do not expose API keys in frontend JavaScript.

Open →

Clear errors

Handle transcript_not_available, upstream_transcript_failed, rate_limited and quota_exceeded explicitly.

Open →

Pricing FAQ

These answers cover billing shape, request counting and fallback expectations without claiming self-serve checkout is live.

What counts as a transcript request?

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.

Do cached and fresh transcripts behave differently?

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.

What happens after included quota?

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.

Is rate limit the same as monthly quota?

No. Monthly quota controls account-level transcript volume. Rate limits control short-window request pressure and return Retry-After plus X-RateLimit headers.

Does fallback processing cover every video?

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.

How do I start on a plan?

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.

Start with the plan closest to your real workload.

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.

Get API access

Request a plan and describe the application you are building.

Open →

Talk through fallback needs

Use contact when your workload includes harder videos, high volume or custom support needs.

Open →

Read the API reference

Review parameters, response fields, errors and rate-limit headers before integrating.

Open →