Plans and credits

Plans

History is the same on every plan: all of it, since genesis. Plans differ in volume, speed and streaming.

With no key you are on the keyless tier: 2 requests a second and 1,000 credits a day per IP. Agents get a Free key by signature, see Keys for agents.

How credits work

• Each method has a price in credits, listed below. Some methods add credits per item, for example one credit per transaction parsed.
• A successful call is charged. A call that returns an error is free. The charge is in the x-credits-cost header.
• On the Free plan the API stops when the month's credits run out and returns out_of_credits. Paid plans keep going and bill extra credits at the rate above.
• Requests a second are counted in two classes. Light calls cost 1 or 2 credits. Heavy calls cost 5 or more. A call over the rate gets a 429 with retry-after.
• MCP tool calls cost the credits of the method they run.
• A SQL run costs 20 credits plus 1 per 50 MB it reads, charged when it finishes. Reusing a recent identical result (max_age) costs 2. A run that hits its time, memory or read limit costs 10 plus 10 a second; a query rejected before it runs is free. Without a key, SQL runs one at a time with 15 s, 20 GB and 10,000 rows per run, from the keyless daily credits.
• Status, the registry, OpenAPI, llms.txt and account calls are free.

Credits per method