Credits and limits

Credits are the meter, and they are the same credits the app spends. There is no separate API plan and no per-seat pricing: whatever the account is on, the API spends the same balance the interface does. A new account starts with 500 credits, and the free tier tops back up to 250 each month. A paid plan tops up to its own allowance instead - call /v1/credits and read monthlyFloor rather than assuming a number.

What each call costs#

Every metered response carries a credits object with what the call charged and what is left, so a client that tracks spend never has to ask a second endpoint.

{ "credits": { "charged": 6, "balance": 494 } }

Why a search reserves more than it costs#

An agentic search does not know what it will cost until it has run: a simple question is answered in one pass, a hard one reads six sources. Charging afterwards would mean anyone could start any number of searches on an empty balance. So the reservation is taken first, at a size that covers a heavy run, and the unused part comes straight back when the run settles.

You are charged for the search you got, never for the one it might have been.

What gets refunded#

• A filtered search that fails upstream is refunded in full. So is a translation that fails.
• An agentic search that ends in an error having produced no people, companies, or repositories is refunded in full. One that produced results and then failed is charged for what it did.
• A request refused for want of credits, a bad key, or a malformed body is never charged, because nothing ran.

Checking before a long run#

Free to call, so a batch job that checks first can stop cleanly rather than failing partway through on a 402.

Rate limits#

Per key, not per account, so one runaway script cannot take the rest of your integrations down with it.

A third concurrent search gets a 429 rather than a queue, because a queue on a ninety-second call is a timeout with extra steps.

Topping up#

From settings, the same as the app. See pricing for what a pack costs. An account can never be overdrafted: a call that would take the balance below zero is refused before it runs.