> ## Documentation Index
> Fetch the complete documentation index at: https://cloro.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# OpenClaw

> Install the cloro plugin for OpenClaw and give your agent tools to monitor ChatGPT, Perplexity, Gemini, Copilot, Google AI Mode, Google Search, and Google News.

The cloro plugin for [OpenClaw](https://openclaw.ai) 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](/guides/making-requests/sync) — the same `POST /v1/monitor/*` requests documented in the [API reference](/api-reference/introduction), returned to the agent as structured JSON.

## Prerequisites

* A running [OpenClaw](https://docs.openclaw.ai) gateway
* A cloro API key from the [dashboard](https://dashboard.cloro.dev) (see [Authentication](/guides/authentication))

## Install the plugin

Install the plugin straight from the [cloro OpenClaw plugin repository](https://github.com/cloro-dev/openclaw-plugin) with the OpenClaw CLI:

```bash theme={null}
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:

```bash theme={null}
export CLORO_API_KEY="YOUR_API_KEY"
```

Or add it to `openclaw.json` under the plugin's config block:

```json theme={null}
{
  "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

| Tool                | Endpoint                                                                      |
| ------------------- | ----------------------------------------------------------------------------- |
| `cloro_chatgpt`     | [`POST /v1/monitor/chatgpt`](/api-reference/endpoint/monitor-chatgpt)         |
| `cloro_perplexity`  | [`POST /v1/monitor/perplexity`](/api-reference/endpoint/monitor-perplexity)   |
| `cloro_gemini`      | [`POST /v1/monitor/gemini`](/api-reference/endpoint/monitor-gemini)           |
| `cloro_copilot`     | [`POST /v1/monitor/copilot`](/api-reference/endpoint/monitor-copilot)         |
| `cloro_aimode`      | [`POST /v1/monitor/aimode`](/api-reference/endpoint/monitor-aimode)           |
| `cloro_google`      | [`POST /v1/monitor/google`](/api-reference/endpoint/monitor-google)           |
| `cloro_google_news` | [`POST /v1/monitor/google/news`](/api-reference/endpoint/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](/guides/providers).

Each call consumes credits at the standard per-provider rates — see [Providers](/guides/providers) and [Credits & limits](/guides/credits-and-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:

```bash theme={null}
openclaw mcp add cloro \
  --url https://cloro.dev/docs/mcp \
  --transport streamable-http
```

Or in `openclaw.json`:

```json theme={null}
{
  "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."

<Note>
  Tool calls run synchronously and count against your [concurrency limits](/guides/concurrency). For large batches (tracking many prompts across engines), use the [async API](/guides/making-requests/async) directly instead of looping tool calls.
</Note>