/v1/search calls with Keenable’s POST /v1/search. This page maps depth, outputType and the other Linkup parameters and response fields to Keenable, lists what has no equivalent, 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 returns400 with Unknown parameter(s), so remove Linkup 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 5 pages published since 1 January 2025. The Keenable request runs without a key.query, mode and up to 5 results. Each result has a title and a url, and usually a snippet and a published_at. Read title where you read name, and snippet where you read content.
No equivalent in Keenable
These Linkup features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.outputType: sourcedAnswer: Keenable returns sources, not a generated answer. Pass thesnippettext to your own model and cite eachurl.outputType: structured: Keenable returns no structured output, with or withoutincludeSources. Pass the snippets to your own model with your JSON schema, and read sources fromresults.includeImages: Search returns web pages only, with no image results.
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.Verify the migration
Check each item before you remove the old client:- Run the Keenable request from Before and after. The status is
200. resultshas at most as many entries asmax_results. Each entry has atitleand aurl.- Your code reads
results[].titlewhere it readname, andresults[].snippetwhere it readcontent, and handles a result that has nosnippet. - Calls that used
sourcedAnswerorstructurednow pass the snippets to your own model. - Your requests send no parameter from a None row. A leftover one returns
400withunknown_parameter. - Change the path to
/v1/searchand sendX-API-Key. The response gains ausageobject. See API keys.
Common questions
Trying Keenable without a key
Trying Keenable without a key
Send the request to
/v1/search/public with an X-Keenable-Title header and no key. Without a key, the endpoint allows 1,000 requests per hour and 10 per second per IP address. See Rate limits.Choosing a mode for each depth
Choosing a mode for each depth
Leave
mode out to get pro, the default, for calls that used fast, standard or deep. Set mode to realtime for calls that used flash. Each mode is billed as its own SKU. See Search.Sourced answers
Sourced answers
Keenable returns sources and has no
answer field. Pass each result’s snippet to your own model and ask it to answer with citations to the url values.Full page text
Full page text
Each result’s
snippet holds page text, capped by snippet_max_length, up to 10000 characters. For the whole page, call GET /v1/fetch with the result’s url. See Fetch.Cost of each call
Cost of each call
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.Related
- Migrate to Keenable: every provider Keenable has a mapping for.
- Migrate from Tavily: another search API with a generated answer, mapped to search.
- Search API reference: every search parameter and response field.