> ## 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
> 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
> Read an API key from the KEENABLE_API_KEY environment variable. Never ask a user to paste a key into chat; send them to https://docs.keenable.ai/api-keys.md
> 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.
> Every error, with its cause and fix: https://docs.keenable.ai/errors.md

# Composio

> Keenable as a Composio toolkit: your agent searches the web and reads pages through Composio, next to the other apps it uses there.

*Toolkit in Composio*

[Composio](https://composio.dev) connects agents to apps and services through one SDK and handles auth for each of your users. Its **Keenable** toolkit (`keenable`) gives your agent web search and page fetch, next to the other tools it already uses through Composio, such as saving results to Notion or Slack.

→ [Keenable toolkit in the Composio docs](https://docs.composio.dev/toolkits/keenable)

## Tools

| Tool | What it does |
| - | - |
| `KEENABLE_SEARCH_WEB` | Ranked web results with page excerpts, optionally limited to one site or a publication date range. Runs on the user's Keenable API key. |
| `KEENABLE_FETCH_URL` | Any URL as clean markdown, optionally with an extraction prompt. Runs on the user's Keenable API key. |
| `KEENABLE_SEARCH_WEB_PUBLIC` | The same search without a key, on Keenable's public rate-limited pool. Takes a required `keenable_title`, your application's name. |
| `KEENABLE_FETCH_URL_PUBLIC` | The same fetch without a key, on the public pool. Takes a required `keenable_title`. |

## Set it up

**1. Create a session with the toolkit**

```python theme={"system"}
from composio import Composio

composio = Composio()  # reads COMPOSIO_API_KEY
session = composio.create(user_id="user_123", toolkits=["keenable"])
```

**2. Connect the user's Keenable key**

Send the user to the connection link once. They enter an API key from the [Keenable dashboard](https://keenable.ai), and Composio stores it for that user.

```python theme={"system"}
request = session.authorize("keenable")
print(request.redirect_url)
request.wait_for_connection()
```

The `_PUBLIC` tools need no key and no connection, only a `keenable_title` argument with your application's name.

**3. Call the tools**

Pass `session.tools()` to your agent, or call a tool directly:

```python theme={"system"}
result = session.execute(
    "KEENABLE_SEARCH_WEB",
    arguments={"query": "latest Model Context Protocol release", "published_after": "7d"},
)

# keyless
result = session.execute(
    "KEENABLE_SEARCH_WEB_PUBLIC",
    arguments={"query": "latest Model Context Protocol release", "keenable_title": "my-app"},
)
```

The keyed tools run on the user's Keenable organization, against its [rate limits](https://docs.keenable.ai/rate-limits.md) and [credits](https://docs.keenable.ai/credits.md). The public tools call Keenable from Composio's servers, so they share one per-IP pool of 1,000 requests an hour with every other Composio user of those tools. Use them to try the toolkit and connect a key for real traffic. Composio's TypeScript SDK works the same way; see the [Composio docs](https://docs.composio.dev/docs/configuring-sessions).


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