Skip to main content
Replace Jina Reader calls to 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 returns 400 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, uses live where Jina uses X-No-Cache, and caps the content at 2,000 characters.
The Keenable response is one page object with 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 in prompt instead: 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.
Mapping checked on 2026-11-19 against github.com/jina-ai/reader/blob/main/README.md, docs.jina.ai/api.md, s.jina.ai/openapi.json, www.elastic.co/search-labs/tutorials/jina-tutorial/jina-reader.

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.
You see the title of RFC 9309 and up to 2,000 characters of its text as markdown. 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. The body has url, title and content, and content is markdown of at most 2,000 characters.
  3. Your code reads content and title at the top level, not data.content and data.title.
  4. Code that read data[].content from a search now calls GET /v1/fetch for each result it needs in full.
  5. Your requests send no parameter from a None row. A leftover one returns 400 with unknown_parameter. Remove leftover Jina X- headers too.
  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. 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.
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.
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.
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.