See what AI actually answers
The LLM Scraper API does not call the models' APIs. It captures the answer a real user sees in ChatGPT, Gemini, Google AI Mode, Perplexity or Copilot, from a specific country at a specific moment, with the sources the interface cites. That is the data the official APIs cannot give you.
- Five engines: ChatGPT, Gemini, AI Mode, Perplexity, Copilot
- Country-level capture through the residential network
- Citations extracted as numbered sources with title and URL, not buried in prose
- Web search on or off, follow-up prompts
- Structured JSON: the answer text with [n] markers plus its citations
- Batch hundreds of prompts in one asynchronous job
npx -y @datafuel/mcp initBuyers ask AI first. Nobody tells you what it says.
Impressions, clicks, position, queries. Twenty years of tooling to know where you stand.
No impressions, no dashboard, no way of knowing what it says about you. The LLM Scraper API is that missing dashboard: the answers, the sources, the changes, by country.
Everything in one request
What the endpoint does, at a glance.Follow-up support reflects the current release; engines add and remove interface features without notice, so the matrix is kept in sync with the docs.
Where the user is changes the answer
The same prompt asked from Milan, New York and Singapore returns three visibly different answers, with different brands recommended. proxy_country runs the capture from a residential exit in that country, so you see exactly what a local user sees.
Geography changes the answer. No official API can show you that.
The sources are the signal that counts
As the answer streams in, every reference the interface shows becomes a numbered citation with its title and URL, matched to the [n] marker in the text. You get citations as data, not as footnotes to parse out of prose.
Citation frequency weighs roughly 35% in whether a source is included in AI answers. It is the number to track.
Model updates rewrite your visibility
Run the same prompts every week and your position in the answers becomes a time series. When a model update lands, the curve jumps, without notice and without a changelog. Continuous monitoring is the only way to see it happen.
Every capture is timestamped, so a change is a data point, not an anecdote.
One prompt, five engines, one table
One prompt goes to ChatGPT, Perplexity, Gemini, Copilot and Google AI Mode, one request per engine. The answers come back in the same JSON shape and line up in a comparable table: who is mentioned, who is cited, where.
Five calls, one per engine, the same JSON shape.
What teams measure with it
The real jobs behind AI-answer monitoring, from brand teams to the platforms that serve them.
Brand visibility & share of voice
How often you appear, in what position versus competitors, on which engines.
Citation source tracking
Which domains the AI cites in your category. The direct input to a GEO strategy.
Competitor benchmarking
How the AI describes and recommends competitors compared with you.
Sentiment & accuracy
What the AI says about you, and whether it is correct. For finance, healthcare and regulated sectors this is brand governance with a verifiable record.
Content gap analysis
A competitor recommended on a category question where you are absent is usually a content gap.
Multi-market monitoring
How positioning shifts between the United States, Europe and APAC, engine by engine.
GEO platforms are customers, not competitors. Bring your own logic, pay per check, and skip running five browser farms yourself. Same API, same 100-credit price, batch and idempotency built in.
The model API answers you. The interface answers your customers.
The first objection from anyone who knows the space, resolved in one table.
Pay only for successful requests
Pick a monthly plan, buy credits once, or run unlimited threads. Failed requests are never billed.
Every plan includes every endpoint and every interface (API, MCP). One shared credit balance: you only pay for volume, and only for successful requests.
Test every endpoint with real credits. No card required.
- Trial credits valid for 1 year
- Every endpoint, API + MCP
- Community support
For production crawlers and agents that need headroom.
- Everything in Starter
- Auto top-up
- Priority chat support
For teams shipping data products on a schedule.
- Everything in Growth
- Usage alerts per API key
- Account manager
High volume at the lowest per-page rate. Checks out instantly.
- Everything in Business
- Dedicated IP pool
- 99.9% SLA
Committed volume, invoicing and governance.
- Custom volume pricing
- Custom concurrency (250+)
- SSO · audit log · DPA
| Free | Starter | Growth | Business | Scale | Enterprise | |
|---|---|---|---|---|---|---|
| Credits / month | 1K one-time | 300K | 1M | 3.5M | 12M | Custom |
| Concurrent threads | 2 | 10 | 25 | 50 | 150 | 250+ |
| API keys | 1 | 3 | 10 | 25 | Unlimited | Unlimited |
| JS rendering | ||||||
| Residential proxies | ||||||
| AI in-flight (your key) | ||||||
| Geo-targeting · 195+ countries | ||||||
| Batch multi-URL | ||||||
| Unlocker · Crawl · Map · Search · LLM Scraper | ||||||
| Auto top-up | — | — | ||||
| Support | Community | Priority chat | Account manager | Slack + phone | Dedicated + SLA |
Frequently asked questions
Engines, targeting and billing, answered straight.
Which models are supported?
How does geographic targeting work?
Are citations always available on every model?
What is the difference with the official model APIs?
How often can I query?
What exactly counts as a successful request?
Can I schedule monitoring?
Are there terms-of-service implications with the AI providers?
Ready to build?
Start with the free tier and scale as your project grows. No credit card, no sales call.
Talk to an engineer, not a chatbot.