Skip to content

Services and permissions

An API key acts for the account that created it: it can call the services that account may use, and reach only that account’s own resources.

CapabilityCosts credits?
Uploads and the file libraryUploading and querying are free
File translation and downloadsTranslation is charged; status checks and downloads are free
PDF and image toolsFree
Document operationsextract and pdf_to_html are free; visual_extract is charged per page actually processed
Instant and batch segment translationBilled by actual usage
Audio, video and voicesBilled by actual usage
Glossaries, projects, tags, search and sharingFree
Usage, balance and settlement recordsFree
SSE and webhooks (file translation jobs)Free

The account’s service status, file formats, per-request limits and concurrency limits apply as well. When a service is unavailable, the API returns a clear error; it never switches to another service on its own.

API keys are for calling the endpoints in these docs. A key cannot change the sign-in email, password, phone number or profile, and cannot create, rotate or revoke API keys; actions that need confirmation in a signed-in browser cannot be done with a key either. Guard your key like your account password.

  • Resources created with a key belong to the key’s account.
  • The balance belongs to the account; each key can have its own budget and allowed translation settings.
  • Queried with a key, credit operations, document operations and the voice list return only records that key started; the job list and usage return the account’s totals.
GET /api/v1/jobs/{job_id}
GET /api/v1/artifacts?job_id={job_id}
GET /api/v1/billing/credits/balance
GET /api/v1/billing/credits/operations
GET /api/v1/usage/summary

When a key’s budget is used up, you can still query the jobs, results and credit records that key created.