cloro

cloro is a developer API that returns structured results from both classic search and the AI answer engines that increasingly sit in front of it. One request can pull a Google SERP alongside the answers ChatGPT, Perplexity, Gemini and Copilot give for the same query, and everything comes back in a single consistent JSON shape rather than five different formats you have to normalise yourself. Parsed sources and citations are included, which is the part that matters for anyone doing AI visibility work: you can see not just what an engine answered, but which pages it cited, and track over time whether your own domain shows up. US state-level targeting lets you check how answers differ by location, and output can be requested as Markdown or HTML when you are feeding it into a content pipeline instead of a dashboard. Typical users are SEO and GEO teams monitoring brand presence across AI assistants, and developers building research, monitoring or competitive-intelligence products who do not want to maintain scrapers per engine. The honest trade-offs: it is an API, not a finished dashboard, so you need engineering time to get value from it, and answer engines are non-deterministic — results shift between runs, so single data points mean less than trends. For teams that already know they need AI-answer data as a feed rather than a report, the unified schema is the main reason to pick it.