Skip to main content
Toolkit in Composio Composio 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

Tools

Set it up

1

Create a session with the toolkit

2

Connect the user's Keenable key

Send the user to the connection link once. They enter an API key from the Keenable dashboard, and Composio stores it for that user.
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:
The keyed tools run on the user’s Keenable organization, against its rate limits, and are billed at its prices: 100,000 free requests a month, then $4 per 1,000. 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.

CrewAI

Give CrewAI agents Keenable web search with the official SDK. Keyless by default.

AG2

Give AG2 agents web search and page fetch with KeenableSearchToolkit, built into AG2 1.2.2 and later, with no API key required.

Google ADK

Give Google ADK agents Keenable search and fetch over the hosted MCP server.

Tool calling

Give an LLM web search and page fetch as tools. Pass the SDK’s TOOLS to any OpenAI-compatible chat completions client and run each call with run_tool_call.