Skip to main content
Replace Exa /search and /contents calls with Keenable’s POST /v1/search and GET /v1/fetch. This page maps each Exa endpoint, parameter and response field to Keenable, and shows the same request on both APIs.

Migrate with your coding agent

Paste this prompt into your coding agent. Your agent reads this page as markdown and rewrites your calls. Your agent finishes by running one Keenable request and showing you the result. The prompt works with Claude Code, Cursor, Codex and any other agent that can read a URL.

What changes

Endpoint map

Parameter map

A parameter Keenable doesn’t list returns 400 with Unknown parameter(s), so remove Exa parameters instead of sending them along. “Closest” means the Keenable parameter does a similar job with a different format or behavior, described in the notes.

POST /v1/search

GET /v1/fetch

Response map

POST /v1/search

GET /v1/fetch

Before and after

This search asks both APIs for 5 pages published since 1 January 2026, with a short excerpt from each. The Keenable request runs without a key.
The Keenable response has query, mode and up to 5 results. Each result has a title, a url and usually a snippet of at most 1,000 characters. There is no contents object: the snippet comes back on every search.

No equivalent in Keenable

These Exa features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.
  • outputSchema: Keenable returns sources, not synthesized output. Pass the snippets to your own model with your schema.
  • category: Keenable has no result categories. Describe the kind of page you want in query.
  • additionalQueries: Send one search per query and merge the results.
  • subpages: Fetch takes one URL. Fetch each subpage URL on its own.
  • userLocation: Keenable has no location targeting.
Mapping checked on 2026-11-19 against exa.ai/docs/search/quickstart, exa.ai/docs/reference/search, exa.ai/docs/reference/get-contents, exa.ai/docs/search.

Use an SDK

This program sends the same search as the Keenable tab above with the official SDK. It runs without a key and prints the title, URL and snippet of each result.
You see up to 5 results published since 1 January 2026, each with a snippet of at most 1,000 characters. Install the SDK for your language from SDKs.

Verify the migration

Check each item before you remove the old client:
  1. Run the Keenable request from Before and after. The status is 200.
  2. results has at most as many entries as max_results. Each entry has a title and a url.
  3. Your code reads results[].snippet where it read highlights or text, and handles a result that has no snippet.
  4. Your code reads snake_case names: published_at, not publishedDate.
  5. Your requests send no parameter from a None row. A leftover one returns 400 with unknown_parameter.
  6. Change the path to /v1/search or /v1/fetch and send X-API-Key. The response gains a usage object. See API keys.

Common questions

Send the request to /v1/search/public or /v1/fetch/public with an X-Keenable-Title header and no key. Without a key, each endpoint allows 1,000 requests per hour and 10 per second per IP address. See Rate limits.
Every Keenable search result carries a snippet of page text, so there is no contents object to send. Set snippet_max_length to cap it. For the whole page, call GET /v1/fetch with the result’s url.
A parameter Keenable doesn’t know returns 400 with code unknown_parameter. When the name is close to a Keenable one, did_you_mean names it: numResults maps to max_results, startPublishedDate to published_after and includeDomains to site. See Errors.
Each search mode and each kind of fetch is billed as its own SKU, and a call made with a key returns what it cost in usage. See Pricing and Balance and usage.