Nobody Reads Reviews Anymore. Not People, Not Agents — So We Built the Reader

Salesforce's 2026 holiday data has a line that should stop everyone building shopping agents: 41% of shoppers skip reading reviews entirely when a brand's AI assistant answers their questions.

Not "read fewer reviews." Skip entirely. The assistant's answer replaces the corpus.

Combine that with what was already true — humans never read all 500 reviews anyway; we read the first ten and the star average — and you get the strange situation this post is about:

Nobody reads reviews anymore. Not people. Not agents.

The agent side of the story

It's tempting to think AI agents fix this. They don't — for a mechanical reason: context windows can't afford the corpus either.

A product with 500 reviews averages maybe 150,000 words. An agent doing a multi-product comparison can't ingest that per product and still function. So what do agents actually do? They read the star average, maybe the first few reviews, and reason from the listing copy — which is exactly the shallow read a tired human does at midnight, except the agent does it confidently, at scale, and calls it research.

And the corpus it skims is contaminated. Estimates put fake, incentivized, or AI-generated reviews at 30–40% of volume on major marketplaces. Trustpilot removed 4.5M fake reviews from a single platform in a year. The star average agents inherit is a blend of real sentiment and industrial manipulation.

The trust transfer

Here's the part that should worry the people building those assistants: when a shopper stops reading reviews because the assistant answered, trust doesn't disappear — it transfers. From an open, if polluted, corpus... to a closed one controlled by the seller.

The assistant's knowledge of the product comes from the product page. The product page is written by the seller. The 41% who skip reviews have moved their trust from "what everyone said" to "what the brand told the AI." That's not an AI problem; it's a single-source problem wearing an AI hat.

So we built the reader

At GoBuy we took the obvious-but-awkward position: if no one in the transaction reads the reviews, the reading itself has to be a service.

What "reading" means when a machine does it seriously:

1. Per-review forensics. Every review gets individual assessment: authenticity signals, Verified Purchase cross-checks, linguistic and temporal anomaly flags. Not corpus vibes — per-item inspection.

2. Statistical aggregation that respects sample size. A Wilson-interval-style lower bound on the positive rate, so a 5.0 from 10 reviews loses to a 4.6 from 2,400. Sample-size honesty, built into the number. (A statistician publicly caught one of our example numbers being wrong recently; the correction is in our writeup. That exchange is part of how this should work.)

3. Longitudinal signals. Rating velocity, burst detection, trajectory shape — the distributional evidence that survives even when AI-generated text becomes stylistically undetectable. A brushed product has a shape over time, regardless of how good the fake prose reads.

4. A disclaimer we actually mean. The output is an Evidence Score: what the marketplace record supports. Not product quality, not safety, not a purchase recommendation. Evidence ≠ quality — and an evidence layer that forgets that becomes just another recommender with better branding.

The two doors

The same reading serves both audiences who stopped reading:

• Humans get the score where they shop (browser extension, badges) — the 30-second answer the 500 reviews were supposed to provide.
• Agents get it as an MCP tool (check_product_trust, free, keyless) and a spec — GPV-1, eight conditions that should hold before any autonomous checkout. Consent doesn't skip evidence.

Same reader. Same score. Two doors.

The uncomfortable summary

The 2026 holiday season is the first with AI-mediated shopping at scale: Adobe projects $275B online, a fifth of traffic influenced by agents. Every one of those transactions leans on a corpus nobody reads — human or machine.

Somebody has to do the reading. We decided it should be something you can audit.

Try it: the server is open source (MIT) at github.com/gobuy-ai/gobuy-mcp, the endpoint is mcp.gobuy.ai/mcp, and the methodology series continues daily here.

More: https://gobuy.ai