OpenClaw

Give OpenClaw live web search, agentic search, news, page retrieval, sitemap discovery, and trending topics with the native openclaw-search1api plugin from ClawHub.

openclaw-search1api is a native OpenClaw plugin that gives the gateway live web access through Search1API — web search, agentic search, news search, readable page retrieval, sitemap discovery, and trending topics.

Unlike an MCP bridge, the plugin registers these as first-class OpenClaw tools.

Install

Install from ClawHub:

openclaw plugins install clawhub:@fatwang2/openclaw-search1api

Restart or reload the OpenClaw Gateway after installation, then verify the runtime:

openclaw plugins inspect search1api --runtime --json

Authentication

Use one of these methods:

Set SEARCH1API_KEY in the OpenClaw Gateway environment.
Install search1api-cli and run s1 login once; the plugin reuses the same OAuth session.
Store an apiKey through OpenClaw's secret-management facilities.

Create a key in the Search1API dashboard if you are using the environment variable.

What the agent can do

Tool	What it does
`search1api_search`	Live web search
`search1api_ask`	Agentic search with only `query` (five credits, 45-second timeout)
`search1api_news`	News search
`search1api_crawl`	Read a public URL as clean Markdown
`search1api_sitemap`	Enumerate a site's URLs
`search1api_trending`	Trending GitHub repos or Hacker News stories

search1api_ask accepts only query (1-500 characters). Its response preserves query, intent, result source and relevance, and optional errors. See Ask.

Credits

Search and news requests cost one credit each; crawling a page costs one additional credit per successfully crawled page. Agentic search costs five credits per request. New accounts receive 100 credits without a credit card. See Credits and limits for current rates.

Version 0.2.0 supports all 19 search engines and all six news sources, including Bing China, Yandex, Grokipedia, and Reuters. time_range supports day, week, month, and year; page supports search pagination. These filters apply to search/news; agentic search accepts only query.

Engine-specific result fields live in optional metadata: GitHub search exposes metadata.kind, metadata.stars, metadata.language, and metadata.num_comments; Hacker News search exposes metadata.story_url, metadata.points, and metadata.num_comments. Optional published_date stays at the result top level. The response-level searchParameters describes the executed request. These paths apply to search/news; trending keeps its separate response shape.

Source

github.com/superagents-lab/openclaw-search1api