Skip to main content
Replace SerpApi or Serper Google search calls with Keenable’s POST /v1/search. This page maps the request parameters and organic result fields of both 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 SerpApi and Serper 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 pages on github.com from the past month. The Keenable request runs without a key and sends the site as its own parameter.
The Keenable response has query, mode and up to 10 results, all on github.com. Each result has a title, a url and usually a snippet. Read url where you read link before.

No equivalent in Keenable

These SerpApi and Serper features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.
  • start: Keenable has no pagination. Ask for up to 50 results in one request with max_results.
  • location: Keenable has no location, country or language targeting.
  • tbm: Keenable returns web pages only, with no image, news or shopping verticals.
  • organic_results[].position: Results come best match first, so the position is the array index.
Mapping checked on 2026-11-19 against serpapi.com/search-api, serper.dev/playground, docs.firecrawl.dev/api-reference/endpoint/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 and URL of each result.
You see up to 10 titles and URLs, all on github.com and published in the past month. 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[].url where it read link, and results[].snippet where it read snippet.
  4. Your code takes a result’s position from its index in results.
  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.
One request returns at most 50 results, and Keenable has no start or page parameter. Narrow the query with site: operators or date filters instead.
Keenable reads quoted phrases, site:, OR, - and parentheses in query. Other Google operators, such as inurl: and intitle:, are read as plain words. See Search operators.
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.