Skip to main content
Run hundreds of searches and fetches for one research task without losing calls to 429. Cap how many calls are in flight, let the SDK wait out Retry-After, and tag every call of the run with one session ID.

Know your limit

Searches and fetches count against the same limit: A keyless research run of more than 1,000 calls an hour hits the hourly cap. Use an API key for volume. Rate limits lists every tier, including pay per request.

Parameters

Run many searches with a cap

This sample runs 8 searches with at most 5 in flight, sends one session ID on every call, and reports any query that still hit a limit after the SDK’s retries. It runs with no API key:
You see one line per query with its result count and top URL. This run was made on 19 November 2026, and the Python output is shown with 3 of 8 lines:
Example output · results vary
A cap on calls in flight isn’t a cap per second. If each call returns in under half a second, 5 calls in flight can pass 10 per second. The SDK then retries the 429 after Retry-After, so the run slows down instead of failing.

Handle a 429

Every SDK retries a 429 for you (TypeScript from keenable 0.2.0): 2 times by default, waiting for Retry-After when the API sends one, and with backoff from 0.5 s up to 8 s when it doesn’t. Set max_retries (maxRetries in TypeScript, MaxRetries in Go) on the client to change that. The error is KeenableRateLimitError in Python and TypeScript, *keenable.RateLimitError in Go and keenable::Error::RateLimit in Rust. Its code says which limit you hit. Over raw HTTP, read the Retry-After header or retry_after_seconds in the body. Keyed responses don’t carry X-RateLimit-* headers, so pace keyed calls with the cap above and the retry wait. Keyless responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset for the hourly window only. See 429 Rate limit exceeded.

Group a run with a session ID

Send the same session ID on every search and fetch in one research run, so Keenable can group the run’s requests. The SDKs have no session_id argument. Send the X-Keenable-Session-Id header with the client’s default headers instead, as the sample does: default_headers in Python, defaultHeaders in TypeScript (from keenable 0.2.0), Options.Headers in Go and Options.headers in Rust. The CLI takes --session-id, and the MCP tools take session_id.

Common mistakes

More than 25 requests per second

Your organization’s limit rises from 10 to 25 requests per second once its completed top-ups reach $1,000 within 90 days. See Raise your limit. For more than 25 per second, contact Keenable. Plans and volume pricing covers dedicated capacity.

API reference