> ## 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

# Versioning and deprecation

> The Keenable API version is in the path (/v1). Deprecated endpoints, parameters, fields and MCP tools keep working for at least 90 days after notice.

This policy covers the Search and Fetch APIs at `https://api.keenable.ai` and the tools of the [MCP server](https://docs.keenable.ai/mcp-server.md) at `https://api.keenable.ai/mcp`. [SELECT](https://docs.keenable.ai/select.md) is a separate service at its own URL. This policy doesn't cover it yet. Keenable announces changes to it in the [changelog](https://docs.keenable.ai/changelog.md).

## Versioning

The API version is part of the path. Search and Fetch live under `/v1`: [`/v1/search`](https://docs.keenable.ai/api-reference/search), [`/v1/fetch`](https://docs.keenable.ai/api-reference/fetch), and their `/public` and `/x402` twins.

Within a version, Keenable makes only backward-compatible changes. They can ship at any time, and Keenable announces them in the [changelog](https://docs.keenable.ai/changelog.md):

* new endpoints;
* new optional request parameters;
* new fields in responses;
* new values for a field that names a mode, status or type;
* changes to ranking, snippets and index coverage that change which results come back.

Write clients that ignore response fields they do not recognise.

A breaking change is one that can make a working integration fail, or change what a request means:

* removing or renaming an endpoint, a request parameter or a response field;
* changing the type of a field, or what a value means;
* making an optional parameter required, or rejecting input that used to be accepted;
* changing a parameter's default.

Breaking changes ship only in a new version of the path, such as `/v2`, or through the deprecation policy below.

The same rules cover the tools of the [MCP server](https://docs.keenable.ai/mcp-server.md) (`search_web_pages` and `fetch_page_content`): their names, their arguments and what those arguments mean.

## Deprecation policy

When an endpoint, a parameter, a response field or an MCP tool is deprecated:

* it is announced in the [changelog](https://docs.keenable.ai/changelog.md) and by email to organization owners, with what replaces it and the date it stops working;
* it keeps working for at least **90 days** after the announcement;
* it is marked deprecated in this reference for as long as it still works.

When a new version of the path ships, the previous one keeps working for at least 90 days after the announcement as well.

Two kinds of change can come with less notice:

* If keeping something running would put customers or third parties at risk, or would break the law, it can change sooner. Keenable sends notice as soon as it can.
* Anything the docs mark as experimental, beta or early access can change or be removed without the 90-day notice period.

## Deprecated now

| What | Status |
| - | - |
| `description` on each [search](https://docs.keenable.ai/api-reference/search.md) result | Always empty; read `snippet`. Kept for compatibility, no removal date. |
| `description` on a [fetch](https://docs.keenable.ai/api-reference/fetch.md) response | Always empty; read `content`. Kept for compatibility, no removal date. |


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