Omnigent

web_search backend Keenable as a built-in web_search backend in Omnigent, selectable via the tool’s search_provider config. → View the change on GitHub

pip install omnigent, then the built-in web_search tool on the keenable backend.

Install

No separate install

Keenable ships as a built-in web_search backend in Omnigent (merged upstream) — there is no separate package to install.

Select Keenable in the agentspec

Set search_provider on the web_search tool. Omnigent never picks an engine for you — with no search_provider the tool returns an error naming the options.

tools:
  builtins:
    - name: web_search
      search_provider: keenable
      api_key: keen_...           # removes the hourly request cap
      # max_results: 5            # 1-20, default 5

Or drive the tool directly

invoke takes a JSON argument string and a ToolContext:

import json
from omnigent.tools.base import ToolContext
from omnigent.tools.builtins.web_search import WebSearchTool

tool = WebSearchTool(config={
    "search_provider": "keenable",
    "api_key": "keen_...",
    "max_results": "3",
})
args = json.dumps({"query": "retrieval augmented generation"})
print(tool.invoke(args, ToolContext("demo", "demo")))

Known defect in the merged backend. Results currently reach the model as titles and links with no page text, because the backend reads a field Keenable leaves empty for most pages. The fix is open upstream as PR #5020; there is no workaround in the meantime.

Add "api_key": "keen_…" to the config to authenticate — this removes the hourly request cap. Leave it out and the backend calls /v1/search/public instead, on the shared public tier at lower rate limits.

Get started

Tools

Integrations

Reference

Install

No separate install

Select Keenable in the agentspec

Or drive the tool directly

​Install

​No separate install

​Select Keenable in the agentspec

​Or drive the tool directly

Install

No separate install

Select Keenable in the agentspec

Or drive the tool directly