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.

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.

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_LOGIN + DATAFORSEO_PASSWORD enable several surfaces as an alternative to BrightData/Olostep:

Each LLM surface defaults to a sensible model (gpt-5.5, sonar, gemini-2.5-flash). Override the underlying DataForSEO model_name via the version slug, e.g. chatgpt:dataforseo:gpt-5-mini:online. All 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.

Starter (scrape the two that matter). Pick one scraper and you're done:

or

Starter + Claude. Add Anthropic direct for cheap Claude coverage:

No scraper (APIs only). Cheapest option, but you're tracking model APIs instead of the real consumer surfaces:

Entries are comma-separated.