Authenta bills media analysis in credits. Credits are shared between the web console and the API, and every job's cost is set when it is created, before it runs.

Only creating a job costs credits. Reading, listing, cancelling and deleting jobs, and uploading files to storage, are free.

How a job's cost is set

A job's cost depends on the task type, not on the file size:

• Most task types have a fixed price per job, set by your plan.
• pdf-tampering-detection is priced per page: the per-page price × the pageCount you send.
• face-intelligence is the sum of the checks you enable: faceswap 60, liveness 30, similarity 30.

The cost field on the job (returned by POST /jobs) is the exact amount charged.

Credits are charged once, when the job is created (POST /jobs). If your balance is too low, the job isn't created and nothing is charged.

The full cost is refunded automatically when:

Your credit history in Settings → Billing shows each charge and refund.

If pay-as-you-go is enabled on your account, jobs keep running when your credit balance runs out, and the usage is billed monthly up to your monthly limit. When the limit is reached, POST /jobs returns 402 PAYG_LIMIT_REACHED.

There's currently no per-key quota on the number of API requests. Keep polling to every 3–5 seconds per job; limits may be introduced later, and when they are they'll be documented here with the error they return.

Both errors come from POST /jobs, use the standard error shape, and mean nothing was charged.

Don't retry these errors in a loop: they won't succeed until the balance or limit changes. Alert your team instead.

Settings → Billing shows your current balance, pay-as-you-go usage, and the history of charges and refunds. If you run batch pipelines, check the balance before a large batch so it doesn't stop halfway.

• Making API Calls
• Jobs API Reference