Skip to main content
Replace Brave web search calls with Keenable’s POST /v1/search. This page maps each Brave query 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 Brave Search API 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.

Response map

Before and after

This search asks both APIs for 10 pages from the past week. The Keenable request runs without a key.
The Keenable response has query, mode and up to 10 results. Each result has a title and a url, and usually a snippet and a published_at. Read page text from snippet, at the top level of each result.

No equivalent in Keenable

These Brave Search API features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.
  • offset: Keenable has no pagination. Ask for up to 50 results in one request with max_results.
  • result_filter: Keenable returns web pages only, with no news, video, FAQ or location blocks.
  • country: Keenable has no country, language or unit targeting.
  • goggles: Keenable has no custom reranking. Use site: operators and exclude_domains.
  • summary: Keenable returns sources, not a summary. Pass the snippets to your own model.
Mapping checked on 2026-11-19 against api-dashboard.search.brave.com/documentation/services/web-search, api-dashboard.search.brave.com/api-reference/web/search/get.

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 and URL of each result.
You see up to 10 titles and URLs, each from a page published in the past week. 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 at the top level, not web.results.
  4. Your code reads results[].snippet where it read description, and handles a result that has no snippet.
  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.
Keenable has no offset. Ask for up to 50 results in one request with max_results.
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: q maps to query, count to max_results and safesearch to safety_mode. 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.