Monthly allowance
With an API key, your organization gets 100,000 requests a month free, worth $400 at $4 per 1,000. The allowance resets each month. To keep going once you’ve used it, top up your balance on the Billing page: pick a package or type any amount from $5 to $999,999.99, the most Stripe takes in one payment. The console also shows how much of the allowance and the balance you have left. Plans are on Keenable pricing. To estimate a month’s cost from your search and fetch volume, see Cost at volume. The allowance is counted in requests because a search and a fetch each cost the same at standard prices. If your organization has its own prices, read what each call cost from the response rather than counting calls. If you don’t send an API key, Keenable doesn’t charge your requests. The request limits cap them, so evaluating without a key doesn’t use the allowance. Pay-per-request calls don’t use it either: you pay for each one in USDC as you make it.What a call costs
Each call is billed under a SKU that names what ran. At standard prices, every SKU costs $4 per 1,000 calls. See Pricing.
The Time Machine endpoints, in Early Access, bill under
search.time_machine and fetch.time_machine.
Prices can be set per organization, so read what a call actually cost from the response rather than assuming a flat rate.
The search mode decides the SKU. Over HTTP, pass mode on /v1/search. Over MCP, an integrator can pin the mode with _meta["keenable/overrides"]. If neither is set, the search runs in pro mode, unless your organization has a different default. The response includes the mode that served the call.
Reading usage per call
Every billed call reports what it cost. The API counts cost in credits: 1 credit is $0.004, so $1 is 250 credits and a call at $4 per 1,000 costs 1 credit. Over HTTP, a/v1/search or /v1/fetch response ends with a usage object:
_meta["keenable/usage"], alongside the result rather than inside the model-visible content:
credits is what the call cost. Multiply it by $0.004 to get dollars. paid shows where the cost came from: false for the free monthly allowance, true for your prepaid balance. Attribute cost per call from this object.
credits_remaining is what your organization has left after the call: the unused free allowance plus your prepaid balance. In the example, 99,120 credits are $396.48. Watch it to see the balance running out before calls start failing with 402. It’s an estimate that can lag your other calls by a few seconds, and it’s left out if the balance couldn’t be read. With -p, the CLI shows it as Credits left. See Metadata for integrators for the full field list.
Calls that cost nothing report no usage: keyless calls, x402 and ZeroClick calls, and failed calls, which are never billed.
Low-credit email
When your organization has used 80% of its monthly free allowance, meaning what it has left (unused allowance plus prepaid balance) drops to 20% of the allowance or below, Keenable emails its admins. With the standard allowance of 100,000 requests, that’s at 20,000 requests, or $80, left. The email gives what’s left in credits of $0.004 each and the date the allowance resets, and links to Billing in the console to top up or turn on auto top-up. It goes out at most once per billing period. Organizations with auto top-up turned on don’t get it while auto top-up can still refill the balance, and do once it has reached its monthly limit.When credits run out
If you’ve used the allowance and your prepaid balance is used up,/v1/search and /v1/fetch return 402 with the code insufficient_credits. The body links to the billing page in billing_url. Top up in the console to resume, or wait for the allowance to reset.
To avoid the 402, turn on auto top-up. It adds to your balance whenever it runs low.