Providers

Elmo tracks which AI answer engines mention your brand. Most AI search traffic comes from ChatGPT and Google AI Mode, and neither exposes a public API. You can approximate their responses by calling the underlying model APIs (OpenAI, Anthropic, Mistral, OpenRouter) with web search enabled, but that's not the real consumer UI — scraping the actual surface is usually closer to what your customers see.

These cover the ChatGPT + Google AI Mode experiences that drive the bulk of AI referral traffic. They're ranked the way we'd pick one today. Elmo runs all five continuously and publishes every result on the status page, so the reliability and speed claims below are measured rather than borrowed from marketing copy — go check them yourself before you trust them.

Which surfaces each one reaches:

Supported scrape targets:

Cloro authenticates with a single bearer API key. Elmo submits each request through Cloro's asynchronous task API and polls until the task completes, which also lets Cloro meter concurrency for us instead of holding a synchronous connection open. Every Cloro surface is the live web-search UI, so the :online suffix is required.

Cloro bills credits from a monthly plan, not per request, and each surface costs a different number: Perplexity 3, Gemini and Google AI Mode 4, Copilot and Google AI Overview 5, ChatGPT 7. The asynchronous API Elmo uses carries no surcharge — the synchronous endpoints add 2 credits per request — and failed requests aren't charged.

Supported scrape targets out of the box:

You can also pass a custom dataset id as the version slug: chatgpt:brightdata:gd_abc123.

google-ai-overview is the one exception: it's the AI summary block on a normal Google results page, so it's fetched through BrightData's SERP API rather than a dataset collector — no dataset id needed. It runs through a serp zone (default sdk_serp, the zone the BrightData SDK auto-provisions; override with BRIGHTDATA_SERP_ZONE) billed to the same BRIGHTDATA_API_TOKEN.

Supported scrape targets:

Oxylabs uses HTTP Basic auth (Web Scraper API username + password). Elmo submits each request through the asynchronous Push-Pull API and polls until the result is ready, avoiding the Realtime API's connection timeout. :online toggles in-product web search for ChatGPT; Perplexity, Google AI Mode, and Google AI Overview always search.

Supported scrape targets:

Olostep models always use web search, so the :online suffix is required.

DataForSEO is pay-as-you-go with no subscription. DATAFORSEO_LOGIN + DATAFORSEO_PASSWORD enable several surfaces:

One account reaches three different DataForSEO products, and the target picks between them for you: DataForSEO always scrapes the live surface where it can.

The scraped ChatGPT and Gemini runs return what a real user sees, including product cards and tables, and ChatGPT reports its query fan-out. They take roughly a minute, since a live session has to finish.

Adding a version slug switches ChatGPT or Gemini to the LLM Responses API, which calls the vendor's model API instead of the consumer product:

That route is much faster and cheaper but doesn't reflect the real ChatGPT or Gemini experience — reach for it when you specifically want to track a named model, or to run both side by side as separate targets. It's the only route that can honor a model_name, so the scraped and SERP surfaces reject a version slug rather than silently ignoring it.

All DataForSEO targets require :online.

DataForSEO prompt text is limited to 500 characters. Country localization is intentionally not exposed in SCRAPE_TARGETS yet because support differs by DataForSEO surface and underlying model.

These hit the provider API directly — cheaper per token than scrapers, but they don't represent the actual ChatGPT / Google AI Mode experience. Use them alongside a scraper when you want extra Claude or OSS model coverage.

*Direct-API estimates also assume ~5 runs/day × 30 days = 150 calls/mo per tracked model, with typical prompt/response lengths. Prompt length drives real cost.

Example scrape targets:

OpenAI/Anthropic/Mistral/OpenRouter entries all require a version slug as the third segment. For Mistral, append :online to route through the beta Conversations API with the web_search tool; without it the request goes to the standard chat completions endpoint and no citations are returned.

DataForSEO straddles both halves of this page. Left alone it scrapes, but pinning a model_name switches ChatGPT or Gemini to a model API instead, and Perplexity always goes that way because no Perplexity scraper exists. See DataForSEO above.

On OpenRouter, :online runs the underlying model's own web search where one exists (Anthropic, Google, OpenAI, Perplexity, xAI) and falls back to OpenRouter's Exa search elsewhere. perplexity/sonar is the cheapest way to track Perplexity: $1/M tokens each way plus $0.005 per request. perplexity/sonar-pro-search is closer to the agentic stack perplexity.ai itself serves, at roughly seven times the cost ($3/$15 per M tokens plus $0.018 per request).

Starter (scrape the two that matter). Pick one scraper, add one direct API key for onboarding analysis and sentiment scoring, and you're done:

or

or

Entries are comma-separated.