SerpApi for OpenClaw personal AI Assistant

SerpApi search plugin for OpenClaw. Registers a web_search provider plus specialized SerpApi tools, distributed through ClawHub.

This is the ClawHub/external-plugin distribution of the SerpApi integration. It replaces the earlier attempt to bundle SerpApi into OpenClaw core (openclaw/openclaw#86440), which was closed with the guidance that optional, credentialed third-party providers should ship as installable ClawHub plugins rather than core code.

What it provides

• web_search provider — "SerpApi Search", backed by SerpApi's Google Light engine (fastest Google Search API).
• 30 specialized tools covering Google News, Scholar, Maps (+reviews), Shopping, Flights, Hotels, Events, Jobs, Trends, Finance, Lens, Autocomplete, Bing, DuckDuckGo, Yahoo, YouTube (search, video, transcript), Amazon, eBay, Walmart, Google Immersive Product, Tripadvisor, Weather, and Facebook / Instagram public profiles.

See skills/serpapi/SKILL.md for per-tool parameters and usage guidance.

Install

openclaw plugins install clawhub:@serpapi/openclaw-plugin

Configure

Set the API key via config or the SERPAPI_API_KEY environment variable:

{
  plugins: {
    entries: {
      serpapi: {
        enabled: true,
        config: { webSearch: { apiKey: "YOUR_SERPAPI_KEY", hl: "en" } },
      },
    },
  },
}

export SERPAPI_API_KEY="YOUR_SERPAPI_KEY"

Get a key at serpapi.com/users/sign_up.

Develop

Requires Node 22.19+ and pnpm.

pnpm install
pnpm run lint
pnpm run typecheck
pnpm run build

Formatting and linting are handled by Biome. pnpm run lint is the check CI runs; pnpm run format applies the fixes.

The plugin targets openclaw >= 2026.6.11 and imports the plugin SDK from the openclaw/plugin-sdk/* subpaths.

Publishing

Publishing a GitHub Release runs the release workflow: test → build → verify → publish-clawhub. ClawHub is the only distribution channel; the package is not published to npm. build produces the artifacts that verify and publish-clawhub consume, so the compiled output is never rebuilt after it has been verified. The release tag must equal v<package.json version> or the workflow fails before publishing.

Running the workflow manually stops after verify and publishes nothing.

Publishing requires the CLAWHUB_TOKEN repository secret.

Publish manually only as a fallback:

pnpm run clean && pnpm run build
clawhub login
clawhub package validate .
clawhub package publish . --family code-plugin --owner serpapi --dry-run
clawhub package publish . --family code-plugin --owner serpapi

The workflow always builds from a fresh checkout; locally, clean first so stale tsc output never reaches the package.

The serpapi organization is created once, by a maintainer, with:

clawhub publisher create serpapi --display-name "SerpApi"

Contributing

See CONTRIBUTING.md for development setup, tests, pull request guidelines, and the release process.

License

MIT