We build one API for the answers AI models and search engines give, so that measuring what they say about you is an afternoon's work rather than a team's roadmap.
People stopped reading ten blue links and started reading one answer. That answer is assembled differently by every model, it cites sources nobody chose, and it changes by country, by state, and by the week. For anyone whose business depends on being findable, the question moved from "where do I rank?" to "what is being said about me, and who is being cited instead of me?"
The data to answer that exists, and collecting it reliably is a full-time engineering problem: eight surfaces, no stable interfaces, geographic variation, and blocks that arrive without warning. Most teams that try end up maintaining a scraper instead of building the product they wanted the data for. cloro exists so that work happens once, here, instead of once per company.
ChatGPT, Perplexity, Gemini, Grok, Copilot, Google Search, Google News and AI Overview each answer differently and none of them publishes a stable interface. We absorb that so a team writes one integration instead of eight, and keeps it when a provider changes its markup overnight.
A response arrives as structured fields — the answer, the sources it cited, the position each result held. That is the part that is hard to build and expensive to maintain, and it is the part a team actually wanted when they set out to scrape a page.
An answer in Lisbon is not the answer in Ohio. Requests run from the country, and for Google from the US state, that the question belongs to, because a brand-visibility number measured from the wrong place is not a smaller number — it is a different one.
We do not recruit peers or run a residential network of our own, and we ask the providers behind our IPs for evidence rather than assurances. Nothing is sourced from compromised devices or from people who were not told what they signed up to.
We publish our terms, privacy policy and data processing agreement rather than sending them on request, and the status page shows uptime as it happens rather than as a quarterly summary. Our security commitments and our IP-sourcing statement go to your security or procurement review in writing, as soon as you ask.
If you want to try the API, the documentation is the fastest route and needs no conversation with us. If you want to join, the open roles are on the careers page — every one of them is remote within Europe. For anything else, the contact form reaches the team directly.
Track your brand and your competitors across global SERPs, with low latency.
