web_search returns titles, URLs and snippets, and web_fetch returns a page as readable text.
→ View the change on GitHub
Install
No separate install
Keenable ships with Rakazo v0.3.3 and later. There is no Keenable package to install.Select Keenable
Rakazo’s default web provider is keyless HTTP search (DuckDuckGo HTML) with local Readability extraction. To switch to Keenable, set these in the deployment’s.env:
KEENABLE_API_KEY is set on both the API and the worker, Rakazo sends it to Keenable and the per-IP limit no longer applies. To go back to the default, set WEB_PROVIDER=keyless-http or remove the line.
Use it
Ask a bot something that needs the web. The thread showsSearching the web: ... while web_search runs and Reading page: ... while web_fetch reads a page.
How it works
web_searchcalls Keenable’ssearch_web_pagestool on the hosted MCP server athttps://api.keenable.ai/mcp. It returns 5 results by default and up to 10.web_fetchcallsfetch_page_contenton the same server. It returns 8,000 characters by default, up to 50,000 when the bot asks for more, and marks longer pages as truncated. Rakazo checks that the URL points to a public address before the request leaves your deployment.- Keenable receives search queries and the page URLs a bot asks to read, plus an
X-Keenable-Title: rakazoheader that names the app. Rakazo sends no user, bot or conversation identifiers. - Rate-limit and other provider errors go back to the bot as tool errors. Rakazo doesn’t fall back to another provider.
- A bot’s Disabled tools setting still turns either tool off.