Skip to main content
The cloro plugin for OpenClaw exposes cloro’s monitoring endpoints as agent tools. Once installed, you can ask your OpenClaw agent things like “check whether Google’s AI Overview for ‘best ai seo tools’ mentions us” and it will call the cloro API and reason over the parsed result. The plugin is a thin client over the sync monitor endpoints — the same POST /v1/monitor/* requests documented in the API reference, returned to the agent as structured JSON.

​
Prerequisites

​
Install the plugin

Install the plugin straight from the cloro OpenClaw plugin repository with the OpenClaw CLI: 
openclaw plugins install git:github.com/cloro-dev/openclaw-plugin
openclaw plugins enable cloro
openclaw gateway restart

​
Configure your API key

Set the key as an environment variable available to the OpenClaw gateway: 
export CLORO_API_KEY="YOUR_API_KEY"
Or add it to openclaw.json under the plugin’s config block: 
{
  "plugins": {
    "entries": {
      "cloro": {
        "enabled": true,
        "config": {
          "apiKey": "YOUR_API_KEY",
          "defaultCountry": "us"
        }
      }
    }
  }
}
Optional config: baseUrl (defaults to https://api.cloro.dev), defaultCountry (used when a tool call omits country, defaults to us), and timeoutSeconds (defaults to 300 — monitor requests drive real provider sessions and can take a while).

​
Available tools

ToolEndpoint
cloro_chatgptPOST /v1/monitor/chatgpt
cloro_perplexityPOST /v1/monitor/perplexity
cloro_geminiPOST /v1/monitor/gemini
cloro_copilotPOST /v1/monitor/copilot
cloro_aimodePOST /v1/monitor/aimode
cloro_googlePOST /v1/monitor/google
cloro_google_newsPOST /v1/monitor/google/news
Assistant tools take a prompt with optional country and state (US state targeting). cloro_google additionally supports location, device, pages, and an aiOverview flag that includes Google’s AI Overview as markdown with sources. Grok is not exposed while the provider is temporarily unavailable. Each call consumes credits at the standard per-provider rates — see Providers and Credits & limits.

​
Alternative: connect the cloro MCP server

If you just want your agent to look up cloro’s documentation and API reference — or you’d rather not install a plugin — OpenClaw can also connect to cloro’s hosted MCP server directly: 
openclaw mcp add cloro \
  --url https://cloro.dev/docs/mcp \
  --transport streamable-http
Or in openclaw.json: 
{
  "mcp": {
    "servers": {
      "cloro": {
        "url": "https://cloro.dev/docs/mcp",
        "transport": "streamable-http"
      }
    }
  }
}
The plugin remains the better fit for monitoring workflows: it exposes each endpoint as a typed tool with your API key and defaults managed in one config block.

​
Example prompts

Once the plugin is enabled, ask your agent directly:
  • “Ask ChatGPT what the best SERP APIs are and list which vendors it cites.”
  • “Compare how Perplexity and Copilot answer ‘best CRM for startups’ — which sources do they cite?”
  • “Does Google’s AI Overview for ‘ai visibility tracking’ mention cloro? Check in the US and Germany.”
  • “Pull the latest Google News articles about our brand.”
Tool calls run synchronously and count against your concurrency limits. For large batches (tracking many prompts across engines), use the async API directly instead of looping tool calls.