DEV Community: gobuy.ai

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

gobuy.ai — Mon, 12 Oct 2026 07:35:53 +0000

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:

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.
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.)
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.
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

How We Built a Fake-Review Detector Using Wilson Confidence Intervals and Bayesian Inference

gobuy.ai — Sun, 11 Oct 2026 10:35:26 +0000

Can math tell you whether those 4.9-star reviews are real?

Not with certainty — but with confidence, and the difference between the two is where the interesting engineering lives. This post walks through the statistical core of GoBuy's scoring: two layers of classical inference applied to marketplace reviews, what each one is actually for, and the trap hiding in the most obvious approach.

The problem

Amazon lists over 300 million products, and conservative estimates put fake, AI-generated, or incentivized reviews at 30–40% of the total — a share that grows as LLMs make generation free. Existing tools (Fakespot, ReviewMeta) answered this with proprietary black boxes. We wanted the opposite: a system where every number is derivable from first principles, so anyone can audit why a product scores the way it does.

Layer 1: the Wilson score lower bound — sample-size honesty for ranking

The naive average ignores how many reviews it rests on. A product with 10 reviews at 100% positive and a product with 1,000 reviews at 95% positive both "average" near the top — but they are not equally believable.

The Wilson score interval fixes this. For observed positive proportion p over n reviews at 95% confidence (z = 1.96):

lower = (p + z²/2n − z·√(p(1−p)/n + z²/4n²)) / (1 + z²/n)

Worked examples:

480/500 positive (96%) → lower bound 0.939
950/1,000 positive (95%) → lower bound 0.935
10/10 positive (100%) → lower bound 0.72 — a perfect-but-tiny record still leaves real uncertainty

The 10-review product drops below products with hundreds of slightly-less-perfect reviews. That is the point: the Wilson layer is a ranking tool that makes claims honest about their sample size.

One thing this layer is not: a fraud detector. A lower bound on the positive rate measures how liked a product appears to be, not whether the reviews are real — a coordinated burst raises the rate and shrinks the interval, which is exactly what an attacker produces. Fraud detection lives in different signals entirely (velocity, trajectory shape, verified-purchase mismatches — a future post).

Layer 2: the Beta-Binomial model — beliefs that update over time

Wilson gives a snapshot. Reviews accumulate, and we want beliefs that update incrementally.

Treat the true positive rate as a Beta-distributed random variable. Start with Beta(1,1) (uniform — no prior opinion), then each positive review nudges the parameters up:

Beta(α₀ + positives, β₀ + negatives)

480/500 → Beta(481, 21). The 5th percentile of that posterior is 0.9425 — note how close it sits to Wilson's one-sided 0.943 bound. That is not a coincidence: with a flat prior, both layers are functions of the same two counts, and they agree to the third decimal.

So why keep the Bayesian layer at all? Because its value is not in the flat-prior case — it is in what the flat prior can't do:

Real priors. A category-level base rate (e.g., "electronics in this price band average 4.1 stars") gives the posterior something to learn from, pulling thin histories toward category reality instead of letting 10 reviews dominate.
Sequential updates. New evidence arrives daily; the posterior updates in O(1) without recomputing history.
Regime changes. A prior informed by recent behavior makes sudden distribution shifts visible faster.

The honest engineering summary: with Beta(1,1), the Bayesian layer is nearly the same signal as Wilson counted twice — it earns independent weight only when it carries real prior structure and the temporal dimension. That is how it runs in production.

What the composite actually measures

Neither layer measures review authenticity. Together they measure how much the observed rating deserves its number — the evidence-quality backbone of a trust score. Authenticity (burst detection, trajectory anomalies, verified-purchase mismatches) is a separate family of longitudinal signals layered on top, and it deserves its own post.

The composite, briefly:

Wilson lower bound — ranking honesty about sample size (~35%)
Bayesian posterior with category priors — temporal + prior structure (~30%)
Longitudinal authenticity signals — burst, trajectory, provenance (the rest; future post)

Try it

The full corpus runs at gobuy.ai; the gate that consumes it is GPV-1, our open pre-purchase verification spec — one call, check_product_trust, returns the evidence score an agent should see before checkout. The reference implementation is open source.

Corrections: an earlier version stated 0.69 for the 10/10 Wilson example; the correct value is 0.72 (thanks to @arhancanli for catching it). This version also clarifies the division of labor between the two statistical layers, following his equally fair observation that they nearly coincide under a flat prior.