Account access
Checking whether account access is available on this deployment.
Beta pricing
- Free test: 100 credits when the account opens. No payment method required.
- Monthly: $5 each month for 1,000 credits.
- Annual: $48 upfront, with 1,000 credits granted in each of 12 monthly periods.
- Monthly-plan top-up: $2 for 1,000 credits in the current monthly credit period.
- Annual-plan top-up: $1.50 for 1,000 credits in the current monthly credit period.
Free test credits do not expire while the account remains open. Included plan credits expire at the end of their monthly credit period. Top-ups expire 30 days after purchase. Unused paid credits are not refundable. Read the Terms and Refund Policy before purchase.
What one credit buys
The billing unit is one completed selected track. A cached track and a freshly extracted track cost the same, because you asked for the same work.
- One credit for a completed transcript in the track you named.
- Zero for a failed request, so a private or caption-free video costs nothing.
- Zero for polling, for every download format, and for webhook delivery.
- Zero for a cancellation that lands before the extraction commits.
Repeating a request with the same Idempotency-Key and the same body returns the original transcript and does not charge a second credit.
What the key can call
- Exact track selection by language and caption kind, or by an observed
track_id. - JSON, plain text, SRT, and WebVTT, all derived from one normalized segment model.
- Batches of up to 1,000 explicit video inputs, with cursor-paged item results.
- Caption access for 24 hours after each completion, operation records for 30 days, and usage records for 12 months.
- Account-scoped webhook endpoints that carry a resource reference, never transcript text.
Keys are named and scoped, and they never appear in a URL, a query string, or a webhook payload. The dashboard issues, rotates, and revokes them.
What you can use today
The public demo runs the selection flow against sample data. The API reference is generated from the frozen v1 contract. The full service runs only in isolated staging.
What has to land before keys go out
These are the open items on the product record, not a roadmap with dates. Nothing here is scheduled, and none of it is billable until it passes its gate.
- A live WorkOS signup, recovery, first-session, and first-key proof.
- A larger multi-exit soak that measures throughput before any production account limit is published.
- Production subscription billing, recurring grants, subscriber-only top-ups, and payment reconciliation.
- A production API deployment on the custom domain, with a tested rollback path.
Policies and support
Creating and using an account is governed by the Terms,Privacy Policy, and Acceptable Use Policy. The beta's measured target is described in the Service Level Policy. For help, use the support route.