Ways to pay
These are standard rates. Prices can be set per organization, so read
credits in the usage object of each keyed response for what a call actually cost. See reading usage per call.
Keenable spends the free allowance first, then purchased credits. The allowance resets each month. Purchased credits never expire.
What each call costs
With an API key, each call is billed under a SKU that names what ran. A search is one request whether it returns 1 result or 50.
Prices can be set per organization, and the experimental Time Machine endpoints bill under their own SKUs. To see what a call cost, read
credits in the usage object of the response. See reading usage per call.
The MCP server isn’t billed separately. With an API key, its tool calls draw on the same credits at the same price as the HTTP API.
Buy credits and auto top-up
Buy credits under Billing in the console. You need a card only to buy credits or to turn on auto top-up. If the allowance and your purchased credits both run out,/v1/search and /v1/fetch return 402 until you buy credits or the allowance resets. To avoid the 402, turn on auto top-up. When your purchased balance falls below a threshold you set, Keenable charges your saved card and adds credits.
What isn’t billed
- Calls without an API key. Keenable doesn’t meter them. The rate limits cap them instead.
- Failed calls. A failed call draws no credits. On the pay-per-request paths, a response of
400or above is never charged. See what is charged. - Pay-per-request calls, as far as your credits go. An x402 or ZeroClick call is paid for on its own and never draws on your organization’s allowance or credits.