It picks the product, the price and the seller
Assistants don't just answer — they recommend a specific offer and link to a specific page. That page is not always yours, and not always current.
Ethically-sourced proxies: Learn More
Infatica Verify captures what AI assistants tell buyers about your products, follows the link to the live seller page, and shows where the product, price or seller doesn't match with a suggested fix, an owner, and a recheck once it's done.
“Where can I buy the WH-Pro 5 headphones in Germany?”
Assistants don't just answer — they recommend a specific offer and link to a specific page. That page is not always yours, and not always current.
Not the assistant. A stale price on a reseller's page reads as a brand that can't keep its own numbers straight.
Counting errors changes nothing. Every discrepancy we publish comes with what to change, where, and who owns it.
Not an alert and not a score. A single checked recommendation, with the three sides of the comparison kept apart and the action attached.
The live price is 17.9% above what the assistant quoted — past the 10% threshold.
Five steps from an AI recommendation to a confirmed fix
See where you appear. Which buyer questions, markets and assistants surface your brand, your products and your sellers.
Output: mention rate, product recommendation rate, linked offers, competitors, cited domains.
Check what the buyer actually finds. We follow the linked offer to the live commerce page and compare it against both the requested product and the assistant's own claim.
Output: product match, variant match, price, availability, seller, destination status.
Understand the discrepancy. We cross-check the answer, its cited sources, your reference, the live page and the redirect chain, and name a probable or confirmed cause.
Output: observed fact, probable or confirmed cause, confidence, supporting signals, missing evidence.
Turn evidence into a task. Each discrepancy becomes a finding with a remediation target, a recommended action, an owner and a status.
Confirm it's gone. When the owner says the fix is live, re-run the same check on demand. The finding records whether the problem disappeared. Manual recheck is included; Monitoring automates it.
Every finding says what you can change — and what you can't
You own the fix. The target is a surface you control: official product page, structured data, redirect, feed or PIM, regional catalogue. Closeable without anyone else's cooperation.
A named partner owns the fix. The target sits with a seller, marketplace or distributor. The finding carries the evidence that partner needs in order to act.
Real, but nothing to assign. The discrepancy is confirmed, no external remediation path was identified. Kept under observation and measured over time.
Not enough to recommend an action. Visible, but the available evidence doesn't support naming a responsible action. What's missing is listed.
Published findings with a concrete direct or partner remediation path, divided by all published findings. A finding counts only when it has all four: remediation target, recommended action, suggested owner, supporting evidence.
Observation-only and Insufficient evidence findings stay published — they are simply outside the numerator.
An AI visibility tool tells you how often you are mentioned. Visibility is here as the input layer that finds the affected answers — we don't sell mention counts on their own, and we don't optimise your position inside assistant answers.
We verify the live offer page — product, price, availability, seller. Not the basket, shipping or the final order total. There is no purchase step anywhere in the chain.
Your catalogue is the reference for comparison, not a place to maintain product data.
We record facts and evidence. Classifying a seller or a price stays with your team. Absence from a public locator is “authorization not confirmed”, never a violation on its own.
Verify runs on Infatica's own infrastructure. The same proxies, scrapers and AI capture we already operate.
Captured ChatGPT, Gemini and Perplexity answers with the available sources and metadata, from the country and language relevant to the buyer.
Browser rendering and access strategies for protected commerce pages. Blocks are recorded in coverage, not hidden.
40M+ IPs across 195+ countries, with realistic browser profiles, so the request leaves from the buyer's market.
View Trust Center →An assistant answers differently in Berlin than it does in São Paulo — different sellers, different prices, different availability. Every capture is run from the country and locale of the buyer you care about, and the locale travels with the finding as evidence.
“Where can I buy the WH-Pro 5 headphones?”
Country, locale, timestamp and final URL are attached to every finding as evidence.
What's in my queue today, what do I do, and how will I know it's fixed?
What share of AI recommendations leads to the right product, price and seller?
Where do the reference, the feed and the pages disagree?
Which sellers is AI sending our buyers to?
Which partners and prices need attention this week?
Where are we present, and where are we losing the recommendation?
Start with a demo on your category, or a starter audit on a selected part of your catalogue.
FAQ
Yes. A first project runs from a brand name, an official domain and target markets. Without a catalogue we compare the assistant's claim against the live page, and the result reads “claim verified · catalog match unavailable” rather than a bare “verified”. A catalogue adds the requested-product side and raises what a finding is allowed to claim.
Whether the live page agrees with the assistant's claim — product name, price, availability, seller — and whether the link resolves at all. We can't confirm that the page shows the product you intended, that the price matches your policy, or that the seller is authorized. Those need a catalogue, a price policy and a seller list.
No. Recheck is part of the Core Platform: when an owner reports the fix is live, you re-run the same check and the finding records the result. Monitoring adds schedules, regression detection and alerting on top.
It is recorded as unverifiable with the reason — page protection, timeout, no link in the answer — and stays outside every accuracy rate. Coverage and the unverifiable share are published next to the accuracy metrics.
Assistant answers are stochastic by nature. Each finding carries its run and timestamp, and Monitoring records the movement between runs as volatility rather than as measurement error.
Through four statuses: confirmed authorized, authorization not confirmed, confirmed unauthorized, and unknown or conflicting evidence. Absence from a public locator is never a violation on its own; confirmed unauthorized requires your confirmation.
Yes. A feed or PIM raises the reference level of your findings; a confirmed seller list and price policy enable Protect. The format is agreed against your stack at the start.