Uniclaw Relay Search

OpenClaw web search provider for shared Pod mode.

The plugin registers provider uniclaw-relay and reads a per-agent token file from the current agentDir:

For OpenClaw 2026.5.12+, the package declares contracts.webSearchProviders=["uniclaw-relay"] in openclaw.plugin.json, openclaw-plugin.json, and package.json#openclaw.contracts so tools.web.search.provider=uniclaw-relay can pass startup config validation when this native provider path is used.

{
  "token": "relay-token",
  "gatewayBaseUrl": "http://claw-gateway:8080/v1/api",
  "ownerType": "user",
  "ownerRef": "user-id",
  "tokenId": 123
}

It sends requests to POST <gatewayBaseUrl>/search with:

{
  "query": "search terms",
  "count": 5
}

When provider is omitted from relay-search.json, Gateway chooses the upstream provider from backend settings. The tool schema does not expose an upstream provider argument, and the runtime ignores model-supplied provider values.

Authentication is Authorization: Bearer <token>. The token is not stored in OpenClaw global plugin config, so multiple users sharing one Pod keep search quota, billing, and channel routing isolated by agent directory.