Native web tools inside OpenClaw
openclaw-search1api installs from ClawHub and registers search, news, page reading, sitemap discovery, and trending as first-class OpenClaw tools. Restart the gateway after install.
What the plugin adds
Five tools, no MCP config
`search1api_search`, `search1api_news`, `search1api_crawl`, `search1api_sitemap`, and `search1api_trending` are native OpenClaw tools.
Install from ClawHub
The package is published as `clawhub:@fatwang2/openclaw-search1api`. One command installs it into the gateway.
Three ways to authenticate
Set `SEARCH1API_KEY` on the gateway, reuse an `s1 login` session, or store an `apiKey` through OpenClaw’s secret management.
Install from ClawHub
Install the plugin, then restart or reload the OpenClaw Gateway. The inspect command confirms the runtime picked it up.
Install and inspect — bash
Worth knowing
The gateway has to restart or reload after install before the tools appear.
This is not an MCP client config. OpenClaw calls Search1API through the plugin.
Tool calls bill as ordinary API calls: 1 credit per search or news request, plus 1 for each page successfully retrieved.
What people do with it
Let an OpenClaw agent look up current docs before it writes code.
Read a URL it was handed in the same turn.
Check GitHub or Hacker News trends at the start of a session.
FAQ
How is this different from the MCP server?
The MCP server is a hosted process a client talks to over HTTP. This plugin installs into the OpenClaw Gateway and registers native tools, so there is no MCP transport to configure.
Do I still need an API key?
Usually yes — set `SEARCH1API_KEY` in the gateway environment. If `search1api-cli` is installed and you have already run `s1 login`, the plugin reuses that OAuth session instead.
How much does it cost?
New accounts get 100 credits free with no card. A search or news request is 1 credit, and each page successfully retrieved adds 1 more.