Cloro API
★ Only Publicly Available OpenAPI DocumentAnalyticsWeb Analyticsbearer8 EndpointsREST
For Agents
Query AI answer engines (ChatGPT, Copilot, Perplexity, Grok, Gemini, Google AI Mode/Overview) for brand monitoring and citation tracking via a single API surface.
Use for: I want to check how ChatGPT answers a question about my product, Compare brand mentions across Perplexity, Copilot, and Gemini, Monitor whether Google AI Overview cites our website, Run a brand visibility query across all AI answer engines
Not supported: Does not handle traditional SEO rank tracking, paid ad analytics, or social media monitoring — use for AI answer engine and generative search visibility only.
Jentic publishes the only available OpenAPI specification for Cloro API, keeping it validated and agent-ready. Cloro is a generative-AI brand monitoring service that tracks how a brand, product, or topic appears across answer engines and AI search interfaces — ChatGPT, Microsoft Copilot, Perplexity, Grok, Google Search, Gemini, Google AI Mode, and AI Overview. Each endpoint accepts a query and returns the answer engine's response so brand teams can measure presence, sentiment, and citation share. Authentication is a bearer token passed in the Authorization header.
Install Jentic One Beta
Connect the Cloro API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloro API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Cloro API.
Probe ChatGPT for a query and capture the model's response for brand presence analysis
Run the same query across Copilot, Perplexity, Grok, and Gemini to compare answer engines
Track brand mentions in Google Search, Google AI Mode, and Google AI Overview
Compare citation sources returned by different generative search engines
Schedule recurring AI search queries to detect brand mention drift over time
Build a side-by-side answer engine matrix for share-of-voice reporting
Use Cases
Patterns agents use Cloro API for, with concrete tasks.
★ Generative Engine Optimisation Monitoring
Marketing teams now optimise for AI answer engines, not just traditional SERPs. POST /monitor/chatgpt, /monitor/perplexity, and /monitor/aioverview let an agent run the same brand or product query across each engine and compare answers, citations, and tone. The output feeds GEO dashboards in the same way rank trackers feed SEO dashboards.
Run the query 'best CRM for startups' against /monitor/chatgpt, /monitor/perplexity, and /monitor/aioverview and return whether 'HubSpot' appears in each response.
Competitor Citation Tracking
Brand and PR teams need to know which competitors AI engines surface for category questions. By calling /monitor/copilot, /monitor/grok, and /monitor/gemini with a category prompt, an agent can extract the named brands and the sources cited, producing a weekly citation share report. This replaces manual prompt-and-screenshot workflows.
Query Copilot, Grok, and Gemini with 'top project management tools 2026' and return the ordered list of brands cited in each response.
Crisis Detection Across AI Search
When negative coverage breaks, brand teams must know whether AI engines have ingested it. Running /monitor/aimode and /monitor/aioverview with crisis-related queries lets an agent detect when generative search starts surfacing a story and trigger downstream alerts to PR. The probe is non-destructive and can be scheduled hourly.
Every hour, query Google AI Mode and AI Overview with the brand name and a crisis keyword; flag responses where the crisis story is cited.
AI Agent Brand Visibility Probe
Embed Cloro inside an AI assistant that gives marketers a one-line brand visibility score on demand. Through Jentic, the agent searches by intent, loads the right /monitor/{engine} schema, and probes the engines in parallel. The bearer token stays in the Jentic vault so the model never receives the key.
Search Jentic for 'monitor brand on chatgpt', load the /monitor/chatgpt schema, and execute it with the user's brand keyword.
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for cloro api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/monitor/chatgpt
Query ChatGPT and capture the response
POST
/monitor/perplexity
Query Perplexity and capture the response
POST
/monitor/copilot
Query Microsoft Copilot
POST
/monitor/gemini
Query Google Gemini
POST
/monitor/aioverview
Query Google AI Overview
POST
/monitor/aimode
Query Google AI Mode
POST
/monitor/grok
Query Grok
POST
/monitor/google
Query Google Search
POST
/monitor/chatgpt
Query ChatGPT and capture the response
POST
/monitor/perplexity
Query Perplexity and capture the response
POST
/monitor/copilot
Query Microsoft Copilot
POST
/monitor/gemini
Query Google Gemini
POST
/monitor/aioverview
Query Google AI Overview
POST
/monitor/aimode
Query Google AI Mode
POST
/monitor/grok
Query Grok
POST
/monitor/google
Query Google Search
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Cloro bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents trigger /monitor calls without ever seeing the Authorization header value.
Intent-based discovery
Agents search Jentic by intent (e.g., 'monitor brand on perplexity') and Jentic returns the matching /monitor/{engine} operation with its schema, ready to execute.
Time to first call
Direct Cloro integration: half a day to wire all eight monitor endpoints. Through Jentic: under 15 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloro API through Jentic.
Why is there no official OpenAPI spec for Cloro API?
Cloro does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cloro API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Cloro API use?
Cloro uses bearer token authentication. Pass your token in the Authorization header as 'Bearer <token>'. Through Jentic, the token is stored encrypted in the MAXsystem vault and injected at execution time so agents never see the raw secret.
Which AI answer engines can I monitor with the Cloro API?
Eight engines, each with its own POST endpoint: /monitor/chatgpt, /monitor/copilot, /monitor/perplexity, /monitor/grok, /monitor/google, /monitor/gemini, /monitor/aimode, and /monitor/aioverview. Send the same query to all eight to compare brand presence and citations.
What are the rate limits for the Cloro API?
Rate limits are tied to your Cloro plan and are not encoded in the spec. Heavier monitoring loops should batch queries and respect any 429 responses with backoff. Jentic surfaces 429 errors back to the agent so it can pace requests.
How do I run a multi-engine brand check through Jentic?
Run pip install jentic, search for 'cloro monitor chatgpt' (or any engine), load the schema, and execute with your query string. To compare engines, fan out search-load-execute calls across the eight monitor endpoints in parallel.
Does the Cloro API return source citations?
Yes. The monitor responses include the answer engine's reply and, for engines that expose them, the cited sources. This lets you build citation-share reports rather than only mention counts.
GET STARTED