Enterprise API credits and pricing

Everything the Enterprise API sells is priced in credits. One credit is one US cent, and that never changes: when a price changes, the number of credits a request costs changes, never the value of a credit. This is separate from the Quorum Podcasts and Storage plans, which are priced per briefing in Swiss francs; an API credit buys claim checks and nothing else.

What a request costs

The tariff in force is version 2, from 5 September 2026.

| Request | Credits | |---|---| | Check one claim, with the evidence sent in the request | 1 ($0.01) | | Check one claim against a batch of documents you loaded earlier | 2 ($0.02) | | Check several claims in one bulk request | 1 or 2 per claim, by the same rule | | Review a whole draft against a batch | 2 per claim Attest extracts and checks | | Upload documents or drafts, list or delete batches, poll a review's status, MCP protocol messages | free (the poll that collects a finished review carries that review's own charge) |

The price is the same whether or not you ask for an explanation with the verdict. A request that fails with an error is not charged.

A worked example: a draft review that extracts and checks 200 claims costs 400 credits, which is $4.00. A single claim checked with its own evidence costs 1 credit. A bulk request of 100 claims against a batch costs 200 credits.

How a draft review is charged

A draft review finds the claims itself, so its cost is only known once it has run. The API reserves the review's ceiling when the review starts: the request's maxClaims, or 200 when none is set, at 2 credits each, so a default review reserves 400 credits; when the draft text is sent in the request, the reservation is also bounded by its length, since a short draft cannot hold that many claims, and that same figure is the most the review may check. As soon as the review has found its claims the reservation shrinks to that count, and when the result is collected it is corrected to the claims actually checked. A review nobody collects settles at its reserve after 24 hours, since the work was done.

When the balance cannot cover the whole ceiling but can cover some of it, the review is not refused: it runs with the ceiling the credits can pay for, and the result says so (summary.truncated), lists the passages left unchecked, and returns a nextCursor that a second review of the same draft continues from, checking nothing twice. A balance below the price of a single claim refuses the review. The daily claim limit clamps and refuses the same way, and the rate limits and a metered workspace's monthly cap refuse as they do for any request.

Getting credits

Starting credits. A new developer account receives 250 credits for linking a card through Stripe. Nothing is charged, then or later, unless you buy a pack, switch auto top-up on or take a plan. It is one grant per person and per card, with no cash value. Linking the card also switches on API keys and MCP connections for the workspace. In India, Pakistan, Bangladesh and Nepal a card cannot be checked for nothing, so the credits are claimed with a card check instead: $1, shown in your own currency, charged through Stripe and refunded as soon as it goes through. It buys nothing and no card is stored, and your bank may take a few days to show the refund.

Credit packs. Buy 2,500 credits for $25, 10,000 for $100, 50,000 for $500, or any amount from $5 up. Pack credits never expire. A pack switches on API keys and MCP connections for any workspace, including one that has claimed no starting credits; "Using the Quorum Enterprise API" covers access.

Auto top-up. An owner or admin can have a chosen amount charged to the saved card whenever the balance falls below a threshold they set, so an integration is never stopped by an empty balance. A card issued in India cannot be charged while you are away, under the Reserve Bank of India's rules, so auto top-up and monthly plans are not offered for it; we email the workspace's owners when the balance runs low instead, with a link to buy a pack.

Plans. A monthly plan includes credits at a lower rate than pay-as-you-go, a discounted rate beyond them, and higher limits for keys and connections.

| Plan | Per month | Credits included | Beyond them | Requests a minute | Claims a minute | Claims a day | |---|---|---|---|---|---|---| | Pay as you go | nothing | none | 1 cent a credit | 60 | 60 | 2,000 | | Starter | $29 | 3,300 | 0.95 cents a credit | 120 | 120 | 5,000 | | Team | $99 | 12,500 | 0.85 cents a credit | 300 | 200 | 20,000 | | Scale | $349 | 55,000 | 0.75 cents a credit | 600 | 300 | 100,000 |

Included credits are granted at the start of each period and used before pack credits. What is left of them expires when the period ends; pack credits stay. Usage beyond the included credits is billed at the plan's rate on the next monthly invoice.

Metered billing. A workspace with a card on file can choose metered billing instead of paying ahead. Credits it holds are used first, and anything beyond them is invoiced monthly at one cent a credit. Requests are never refused for lack of credits; instead a monthly cap, set by an admin, bounds the bill, and beyond it the API answers 429 until the month turns. Switching metered billing off from the billing portal keeps the credits held and returns the workspace to paying ahead.

When a request is refused

Over MCP a refusal arrives as a tool error whose text names the limit, what remains and when to try again, so your assistant can tell you; over HTTP it is the status and code below.

• 402 credits_exhausted: the balance cannot cover the request, or even one claim of a draft review. Buy a pack, switch auto top-up on or take a plan. The card is never charged for a refused request.
• 429 claim_budget_exhausted, rate_limited or claims_rate_limited: a limit for the day or the minute was reached. The response says when to retry, and a plan raises the limits.
• 429 monthly_cap_reached: a metered workspace reached its cap for the month.

Reading the statement

The Billing page shows the credits held and a statement of every credit in and out. API usage reaches the statement within a few minutes of the work, as one line per hour that grows while the hour is open. A draft review lands in the hour in which its result was collected, not the hour it started. Every member of the workspace can read the statement; buying credits and changing plans needs an owner or admin.

Subscribers through RapidAPI

A subscriber who reaches Attest through RapidAPI is billed by RapidAPI at the prices on that listing and holds no Quorum credits.