Skip to main content
Replace Parallel Search and Extract calls with Keenable’s POST /v1/search and GET /v1/fetch. 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 Parallel 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.

POST /v1/search

GET /v1/fetch

Response map

POST /v1/search

GET /v1/fetch

Before and after

This search asks both APIs for 5 pages about one goal and leaves one site out. The Keenable request runs without a key and sends the goal as objective.
The Keenable response has query, mode and up to 5 results, none from reddit.com. Each result has a title, a url and usually a snippet. Keenable logs objective but doesn’t use it to rank yet, so put the words that matter in query.

No equivalent in Keenable

These Parallel features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.
  • search_queries: Keenable takes one query per search. Send one request per query and merge the results.
  • max_chars_total: Search has no total budget across results. Cap each result with snippet_max_length.
  • advanced_settings.location: Keenable has no location targeting.
  • client_model: Keenable doesn’t tune results to the calling model.
Mapping checked on 2026-11-19 against docs.parallel.ai/search/migrate-to-parallel, docs.parallel.ai/extract/extract-quickstart, docs.parallel.ai/search/advanced-search-settings, docs.parallel.ai/api-reference/search/search, docs.parallel.ai/api-reference/extract/extract, docs.parallel.ai/resources/source-policy.

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 5 titles and URLs, none from reddit.com. 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 sends one query string per search, not a search_queries list.
  4. Settings that sat under advanced_settings are top-level parameters: max_results, exclude_domains, published_after.
  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 accepts objective and logs it, but it doesn’t change the results or the price yet. Put the words that matter in query. See Search.
Keenable takes one query per search. Send one request per query, in parallel if you like, and merge the results by url.
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.