Credits and billing

JSON and streaming verification use the same fixed prices. Cached and uncached requests have the same price. There is no additional API operation charge.

A verdict requires stance analysis internally, even when the response omits stance fields. include_numeric_assess on JSON verification does not add a separate charge.

Document extraction and classification inspect the outcome before billing. Unsupported/error outcomes and partial outcomes without readable evidence are not charged. A useful partial result can be billable.

V2 numeric verification does not publish a fixed credit price. OCR preparation costs 5 credits for a new successful preparation; retained replays do not charge again. Do not assume V2 operations have the V1 price or a universal receipt shape.

V1 object responses that use the billing wrapper include operation_id and usage.credits. null means the accounting value is unavailable, not that the work was free. A returned 0 is a known zero deduction.

{"operation_id":"EXAMPLE_OPERATION_ID","usage":{"credits":4}}

This is an illustrative receipt. Preserve missing and null values when you store it. Streaming sends a separate usage event; an accounting_error means accounting did not complete normally.

Batch verification returns a result array. Citation list/get, feedback, and upload retain their own response shapes and do not universally add this object receipt. Free ask polling returns the job view. Do not require a top-level receipt on every endpoint.

The current streaming receipt has a legacy zero fallback when the deduction value is unavailable. A zero in an SSE usage event alone does not establish a free operation. Retain the operation ID and reconcile it with your account usage.

Verification responses can include usages, which reports the input, output and total tokens of the model calls the request made. It is not a credit charge; credits are reported separately. usage_unknown: true means a model call could not be measured, so the totals are a lower bound. cached: true means the response came from the server cache and spent no tokens.

The Free plan includes 100 credits each month. See pricing for paid plan allocations and subscription prices. Manage credits and overage settings in your account. Repeating a successful request can incur another charge; store completed results and avoid automatic replay after an ambiguous timeout.