Base URL
Every path on this page is relative to this base URL:Authentication
You can call the API in three ways. Each way uses its own path. With an API key, in theX-API-Key header:
Authorization: Bearer keen_<your_key> works too. If you send both headers, the API uses X-API-Key. See Authentication for obtaining and rotating a key, and for the error responses both endpoints share.
Without one, on the /public twin of each endpoint:
X-Keenable-Title names the application making the call, and Keenable attributes keyless traffic by it. The public endpoints require it. If you leave it out, the API returns 400 with Missing app identifier. The API truncates values longer than 256 characters. If you can’t set a header, pass the same value in the ?keenable_title= query parameter.
Paying per request, on the /v1/x402/* paths, with no key and no account: each call pays $0.01 in USDC on Base over the x402 protocol. See Pay per request for the payment flow and a client example.
Parameters and response shapes are identical across all three. To move between them, change the path and swap one header. If no key is configured, the CLI, the MCP server and every integration fall back to the keyless tier.
Endpoints
Monitors needs an API key: it has no keyless or pay-per-request path. See Monitors for how monitors work and their limits. The Monitors reference has a page per operation: create, list, get, update, delete, run now, list runs, get a run, list results, list deliveries, count and bulk actions.
To move from Tavily, Exa, the Brave Search API, Perplexity, SerpApi or Serper, Linkup or another search API, see Migrate to Keenable. Each page maps their parameters and response fields to these endpoints.
Each endpoint page has the full request and response shape, examples in the official TypeScript, Python, Go and Rust SDKs plus curl, and a playground you can call with your own key.
For a field or term such as
acquired_at, a card or a SKU, see the Glossary.
Limits and billing
If you send an API key, Keenable limits your requests per organization rather than per IP address, and they draw on your balance. See Rate limits for the numbers. If you don’t send a key, Keenable limits your requests per IP address, separately for each endpoint, at 1,000 requests per hour and 10 per second. Keyless requests cost nothing. Keenable still logs them, with the query or URL, your IP address and yourX-Keenable-Title value (see Authentication). See Data and privacy and Security and privacy for what Keenable keeps.
Keyless responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset for the hourly limit, and a 429 adds Retry-After. You share that pool with everyone else on your egress address, so other traffic can use up your headroom. Use a key for anything past a first look.
Pay-per-request calls don’t draw on your balance either. You pay for each one on its own, and they have their own limits.
Errors
Every error body from these endpoints has a stablecode, a one-sentence fix, retryable, and a docs_url that links to the matching section of Errors. A retryable error adds retry_after_seconds and a matching Retry-After header. Branch on code, not on the text of error or message. See Error codes for every code, grouped by type, with whether retrying helps and what to do. Retry rules says when to send a failed request again.