Plans
- The plan is your organization’s, and your keys inherit it.
- On
enterprise, the quota belongs to the whole organization: the web app, its members’ keys and the organization keys all count against the same quota and stop when it runs out. - The quota renews on the 1st of every month at 00:00 UTC.
What is charged and what is not
Only successful responses (status below
400) are charged.- An error response (
4xxor5xx) is logged with 0 credits. - If the data source could not read what you asked for, the response is
503 source_unavailableand you are not charged. - A
200that carriesdegraded_sourcesis charged: the query was answered and what was missing is declared in the response. See Errors. 401,402and429responses are cut off before the query runs.
What each query costs
The cost is decided by method and path: the longest priced path prefix wins. A path without a price of its own costs 1 credit.GET /v1/evidence/signing-key y GET /v1/evidence/timestamp/{name} are open: they need no key and cost
nothing. They let anyone verify a document’s signature without an account.
Checking your balance
Every authenticated response carries these headers:
For a per-endpoint breakdown, use
GET /v1/account (free):
creditsis the balance, computed the same way as the headers:reservedis what your running queries are holding. Onenterprise,sharedistruewhen the balance is the organization’s.limits.request_source_callsis the cap on reads from the data sources per query (see below).failedcounts the queries that ended in an error, logged with 0 credits.
When you hit a limit
Each query also has a cap on reads from the data sources (4,000 by default; the organization can have another one).
If a trace reaches the cap, the remaining reads are not made: the root query returns
503 or the step lands in
degraded_sources, with reason: "budget_exhausted". It is never an empty result.