> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keenable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Every page is listed in https://docs.keenable.ai/llms.txt. To pick a product for a job, read https://docs.keenable.ai/choose.md
> Setup steps for agents, covering the SDKs, the MCP server and the CLI: https://docs.keenable.ai/skill.md
> Keenable search and fetch work without an API key. To add them to code, use the official SDK for the project's language: https://docs.keenable.ai/sdks.md
> Without a key, call POST https://api.keenable.ai/v1/search/public or GET https://api.keenable.ai/v1/fetch/public with an X-Keenable-Title header that names your app.
> With a key, send it in the X-API-Key header and read it from the KEENABLE_API_KEY environment variable. Never ask a user to paste a key into chat. Every access method: https://docs.keenable.ai/auth.md
> To get an API key without the console, use device login: https://docs.keenable.ai/authentication.md#device-login
> MCP server: https://api.keenable.ai/mcp (no key, or X-API-Key; keyless Codex uses https://api.keenable.ai/mcp-public), or https://api.keenable.ai/mcp-oauth for OAuth sign-in. These docs are an MCP server at https://docs.keenable.ai/mcp and the OpenAPI spec is at https://docs.keenable.ai/api-reference/openapi.json
> Keenable searches and fetches public web pages. If a question needs no web information, skip the call.
> On 402 with an API key (code insufficient_credits), stop and ask a human to add credits; don't retry. On 429, wait the number of seconds in Retry-After, then retry. Before you ship, follow https://docs.keenable.ai/production.md
> Every error, with its cause and fix, is in https://docs.keenable.ai/errors.md and moving from another search API is covered in https://docs.keenable.ai/migrate.md
> Before you compare Keenable with another search API, read https://docs.keenable.ai/guides/evaluate-search-apis.md

# hyperresearch web provider with Keenable

> Use Keenable as the web provider in hyperresearch, the deep-research pipeline, for search and page fetch. No key or extra install, 0.13.1 and later.

*Web provider in hyperresearch*

Keenable is a web provider in [hyperresearch](https://github.com/jordan-gibbs/hyperresearch), the deep-research pipeline for Claude Code and Codex. It handles both halves of the pipeline's web work: searching, and fetching pages into the research vault. Search results already carry page text, so there is no extra fetch per result. It works without an API key and needs no extra package.

→ [Web providers in the hyperresearch README](https://github.com/jordan-gibbs/hyperresearch#web-providers)

## Install

The `keenable` provider ships in hyperresearch 0.13.1 and later. Install it, then add it to your coding agent from the project folder:

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"dark-plus"}}
pip install -U hyperresearch
hyperresearch install                    # Claude Code
hyperresearch install . --target codex   # OpenAI Codex
```

## Select Keenable

Set the provider in the project's `.hyperresearch/config.toml`:

```toml theme={"theme":{"light":"github-light-high-contrast","dark":"dark-plus"}}
[web]
provider = "keenable"
```

Run a research task as usual, with `/hyperresearch <question>` in Claude Code or `$hyperresearch <question>` in Codex. Searches and page fetches now go to Keenable, and every fetched source lands in the vault under `research/notes/`.

## Providers compared

| `[web] provider` | Search | Fetch | Key | Extra install |
| - | - | - | - | - |
| `builtin` (default) | No | Plain HTTP | No | No |
| `keenable` | Yes, with page text | Yes | Optional | No |

The README lists the other providers (crawl4ai, Exa, Tavily, Parallel, Serply) and what each needs.

The provider caps each request at 50 results. To lift the keyless rate limits, export a key before you run the agent:

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"dark-plus"}}
export KEENABLE_API_KEY="your-keenable-api-key"
```

> [!NOTE]
>
> Without a key, requests run on the shared public tier at [lower rate limits](https://docs.keenable.ai/rate-limits.md), which a deep research run can reach. See [API keys](https://docs.keenable.ai/api-keys.md).

## Related pages

> [card] [Qwen-MM-Plugins](https://docs.keenable.ai/integrations/qwen-mm-plugins.md)
>
> Use Keenable for web\_search and web\_extractor in the Qwen-MM-Plugins search plugin with QWEN\_MM\_SEARCH\_BACKEND=keenable. Works without an API key.

> [card] [Obscura](https://docs.keenable.ai/integrations/obscura.md)
>
> Add a web\_search tool to Obscura's MCP server with OBSCURA\_WEB\_SEARCH=keenable, so the agent finds pages before it browses them. No key needed.

> [card] [de-anthropocentric research engine](https://docs.keenable.ai/integrations/de-anthropocentric-research-engine.md)
>
> Keenable is one of the MCP servers the de-anthropocentric research engine recommends for web retrieval, with no install and no key.

> [card] [Integrations](https://docs.keenable.ai/integrations.md)
>
> Connect Keenable web search to your agent stack: LangChain, LlamaIndex, Haystack, MCP and more.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.