Skip to main content
Replace Firecrawl /scrape calls with Keenable’s GET /v1/fetch and /search calls with POST /v1/search. This page maps each endpoint, 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 Firecrawl 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. The Keenable request runs without a key and caps the content at 2,000 characters.
The Keenable response is one page object with url, title and content. 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 Firecrawl features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.
  • formats: Fetch returns markdown only, with no HTML, screenshot, links or branding formats.
  • actions: Fetch doesn’t click, scroll, type or wait on a page.
  • location: Neither endpoint takes a location, country or proxy choice.
  • sources: Search returns web pages only, with no image or news sources.
  • categories: Search has no categories. Describe the kind of page in query, or use site: operators.
Mapping checked on 2026-11-19 against docs.firecrawl.dev/api-reference/endpoint/scrape, docs.firecrawl.dev/api-reference/endpoint/search.

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 9110 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.markdown and data.metadata.title.
  4. Your code treats an error status as a page that couldn’t be read, instead of checking success.
  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 crawl endpoint. Fetch takes one URL per request, so fetch each page you need. To find pages on one site, search with site.
Fetch returns markdown only. For a summary or structured fields, set prompt, and content holds only what the prompt asks for. 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.