Skip to main content
Replace another search API with Keenable by changing the request you send and the fields you read. Each provider below has its own page with endpoint, parameter and response maps, the same request on both APIs, and a prompt for your coding agent.

What changes for every provider

A list of domains to search and an exact-match flag become operators in the query string: site:a.com OR site:b.com and "exact phrase". See Search operators. A parameter Keenable doesn’t list returns 400 with Unknown parameter(s), so remove the other provider’s parameters instead of sending them along. When the other provider’s name maps to a Keenable parameter, such as count or limit for max_results, the error’s did_you_mean field names the parameter to use. See Search and Fetch for every parameter, and Authentication for keys.

Providers at a glance

Each row counts the provider’s parameters on its page by how they map: exact, closest (a similar job with a different format or behavior), or none.

Tavily

Tavily Search maps to POST /v1/search and Tavily Extract to GET /v1/fetch. Keenable returns sources and has no generated answer field. See Migrate from Tavily.

Exa

Exa /search maps to POST /v1/search and /contents to GET /v1/fetch. Field names change from camelCase to snake_case, and every search result carries a snippet without a contents object. See Migrate from Exa.

Brave Search API

Brave web search, a GET with query parameters, maps to POST /v1/search with a JSON body. Results sit in a top-level results array instead of web.results. See Migrate from the Brave Search API.

Perplexity

The Perplexity Search API’s POST /search maps to POST /v1/search. Dates change from MM/DD/YYYY to YYYY-MM-DD. See Migrate from the Perplexity Search API.

SerpApi and Serper

Google search through SerpApi or Serper maps to POST /v1/search. Read results[].url where you read link. See Migrate from SerpApi or Serper.

Firecrawl

Firecrawl /scrape maps to GET /v1/fetch and /search to POST /v1/search. Fetch returns the page as markdown in content. See Migrate from Firecrawl.

Parallel

Parallel Search maps to POST /v1/search and Extract to GET /v1/fetch. Settings under advanced_settings become top-level parameters. See Migrate from Parallel.

Jina Reader

Jina Reader’s r.jina.ai maps to GET /v1/fetch and its search on s.jina.ai to POST /v1/search. Options sent as X- headers become query parameters or body fields, and the response is JSON with no data wrapper. See Migrate from Jina Reader.

Linkup

Linkup /v1/search maps to POST /v1/search. depth becomes mode, and outputType goes away because Keenable always returns a results list. See Migrate from Linkup.

Bing Search API

Microsoft retired the Bing Search APIs on 11 August 2025, according to its retirement notice. To move code that called Bing web search, send the search text as query to POST /v1/search and read results[].title, results[].url and results[].snippet. Start from Search.

Verify the migration

Run one search without a key:
Check three things in the response:
  1. The status is 200.
  2. results has at most two entries, because max_results is an upper bound. Each entry has a title and a url.
  3. Most entries have a snippet. This is the text your code now reads. It is optional in the response, so handle an entry without one.
Then add your key: change the path to /v1/search and send X-API-Key. The response gains a usage object. See API keys. To compare your old provider and Keenable on your own queries before you switch, follow Evaluate search APIs. For public numbers, see Benchmarks.