Use JustSerpAPI as your OpenClaw web search provider
The JustSerpAPI OpenClaw plugin lets teams replace Brave, Tavily, or another web search backend with Google SERP-backed results from JustSerpAPI. Install it from GitHub marketplace, set one API key, and point OpenClaw's web_search tool at justserpapi.
Google SERP-backed results
OpenClaw receives live organic search results mapped into title, URL, snippet, source, favicon, and ranking fields.
Marketplace install
Users can install from the public GitHub marketplace manifest without npm publishing or manual plugin packaging.
Simple credential setup
Add your JustSerpAPI key in the OpenClaw plugin config. Environment variable setup is also supported when needed.
Clear operational controls
Configure language, country, SafeSearch, result count, and base URL while keeping the provider id stable.
Why replace another provider?
Use one SERP API for search automation and AI workflows
OpenClaw's provider system makes it easy to swap search backends. JustSerpAPI is a strong fit when your agent needs structured Google Search data, localized results, and search metadata that can be reused outside OpenClaw in your own tools, dashboards, and data pipelines.
Google organic result ranking for agent citations and RAG context.
Country, language, SafeSearch, and count options for controlled searches.
Consistent title, URL, snippet, source, favicon, and position mapping.
One JustSerpAPI key for OpenClaw plus direct API integrations.
Install from the OpenClaw marketplace
The plugin is published through a GitHub marketplace manifest, so users do not need npm. OpenClaw clones the public repository, reads .claude-plugin/marketplace.json, and installs the native plugin from the repository root.
openclaw plugins marketplace list justserpapi/justserpapi-openclaw-websearch
openclaw plugins install justserpapi --marketplace justserpapi/justserpapi-openclaw-websearch
openclaw plugins enable justserpapiConfigure OpenClaw to use justserpapi
Add the plugin entry and set tools.web.search.provider to justserpapi. The recommended setup is to put the API key directly in the OpenClaw plugin config under webSearch.apiKey.
JUSTSERPAPI_API_KEY instead of putting the key in the config file.{
"plugins": {
"allow": ["justserpapi"],
"entries": {
"justserpapi": {
"enabled": true,
"config": {
"webSearch": {
"apiKey": "YOUR_JUSTSERPAPI_KEY"
}
}
}
}
},
"tools": {
"web": {
"search": {
"enabled": true,
"provider": "justserpapi"
}
}
}
}For AI agents
Let OpenClaw agents search the current web with structured snippets that are easy to cite, summarize, and rank.
For SEO teams
Run localized search checks with the same JustSerpAPI data model used by your standalone SEO workflows.
For developers
Keep the integration small: one provider id, one API key, clear error messages, and marketplace-based install.
Frequently asked questions
What is the JustSerpAPI OpenClaw web search provider?
It is a native OpenClaw plugin that registers JustSerpAPI as a web_search provider, so OpenClaw can use JustSerpAPI instead of another search backend.
Why replace Brave or Tavily with JustSerpAPI?
Use JustSerpAPI when you want Google SERP-backed results, ranking metadata, localization options, and one API key shared with your existing JustSerpAPI account.
Does it require npm?
No. The recommended install path uses OpenClaw marketplace support and the public GitHub repository.
Where should the API key be stored?
We recommend putting it in OpenClaw plugin config under webSearch.apiKey. If you prefer environment variables, set JUSTSERPAPI_API_KEY.