r.jina.ai with Keenable’s GET /v1/fetch and search calls to s.jina.ai with POST /v1/search. This page maps each endpoint, header, 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 returns400 with Unknown parameter(s), so remove Jina 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.
GET /v1/fetch
POST /v1/search
Response map
GET /v1/fetch
POST /v1/search
Before and after
This request asks both APIs for one page as markdown in JSON, read from the source now rather than from a cache. The Keenable request runs without a key, useslive where Jina uses X-No-Cache, and caps the content at 2,000 characters.
url, title and content at the top level, not under data. content is the page’s main text as markdown, at most 2,000 characters, and truncated is true when the page was longer.
No equivalent in Keenable
These Jina features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.X-Respond-With: Fetch returns markdown only, with no HTML, plain text or screenshot formats.X-Target-Selector: Fetch takes no CSS selectors. Describe the part you need inpromptinstead: a model reads the page, so the answer can be reworded.X-Engine: Fetch has no engine, wait or timing choice.type: Search returns web pages only, with no image or news results.gl: Search has no country, language or location targeting.page: Search takes no uploaded files, so there is no page of a file to pick.
Use an SDK
This program sends the same fetch as the Keenable tab above with the official SDK. It runs without a key and prints the page’s title and content.Verify the migration
Check each item before you remove the old client:- Run the Keenable request from Before and after. The status is
200. - The body has
url,titleandcontent, andcontentis markdown of at most 2,000 characters. - Your code reads
contentandtitleat the top level, notdata.contentanddata.title. - Code that read
data[].contentfrom a search now callsGET /v1/fetchfor each result it needs in full. - Your requests send no parameter from a None row. A leftover one returns
400withunknown_parameter. Remove leftover JinaX-headers too. - Change the path to
/v1/searchor/v1/fetchand 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 or /v1/fetch/public with an X-Keenable-Title header and no key. Search works without a key too. Without a key, each endpoint allows 1,000 requests per hour and 10 per second per IP address. See Rate limits.Full page text in search results
Full page text in search results
Keenable search returns a
snippet for each result, not the whole page. Raise snippet_max_length, up to 10000, for more text per result, or call GET /v1/fetch with the url of each result you need in full. See Search.One part of a page
One part of a page
Fetch takes no CSS selector. Set
prompt to describe the part you need, such as “the pricing table”, and content holds only that part. 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 Firecrawl: another page-to-markdown API mapped to fetch.
- Fetch API reference: every fetch parameter and response field.
- Search API reference: every search parameter and response field.