4 steps, under 10 minutes

From a paste to a proof badge

The full arc — from a LinkedIn-worthy claim to a tamper-resistant badge you embed on your own site.

01

Plausibility score

You paste the exact claim — as written on LinkedIn, Twitter, your homepage. Our model weighs it against 25 years of marketing benchmarks and returns a 0–100% likelihood plus 3 reasons. Unauthenticated, free, 60 seconds.

Runs through CRM Agent Studio (primary) → Groq llama-3.3-70b (fallback) → deterministic heuristic (last resort). Always returns a result.

02

Connect the source

Disagree with the score? Prove it. Click one button to connect Google Search Console, Analytics, Ads, or Stripe — whichever data source actually backs your claim.

OAuth 2.0 user-delegated. Read-only scopes. Tokens AES-256-GCM encrypted at rest. Revoke any time from your dashboard or your Google account.

03

We verify against the data

We query the live API — not a screenshot — and compare the real numbers to exactly what the claim asserted. Ranking claims: avg position over 28 days for the exact keyword. Traffic claims: summed clicks/impressions for the stated window.

Evidence is stored as structured JSON. Methodology is documented. Confidence score is explicit. You can re-run verification any time.

04

Earn a badge + case-study page

On pass, we mint a tamper-resistant badge you can embed on your site with one <script> tag. The badge links to a hosted case-study page with the full claim, evidence, date, and methodology.

Badge is signed. Evidence page is version-stamped. If the underlying data changes, the badge page updates — you can't fake this without your real account.

Under the hood

What makes this tamper-resistant

User-delegated OAuth

We never see credentials. Google issues us scoped read-only tokens on your explicit consent. Revocable at any time.

Real-API queries

Every verification is a live call to Google's API. No screenshots. No copy-paste. No way to fake the number.

Version-stamped evidence

Each verification is dated + confidence-scored. Public pages update when data updates — nothing is preserved in amber.

FAQ

Do you store my analytics data?

Only the minimum needed to verify the claim. OAuth refresh tokens are stored encrypted. You can revoke access at Google at any time and the connection dies immediately.

What if my claim changes over time?

Verifications are dated. If you re-verify weekly or monthly, the public badge shows the latest verified value plus a re-verify timestamp.

Can competitors weaponize this against me?

No. Scoring uses only what you publicly claim, and verification only uses data you voluntarily connect. There is no mechanism for anyone to run a verification on someone else's account.

What data sources do you support?

Launching with Google Search Console. Google Analytics 4, Google Ads, Stripe, and GitHub are next on the roadmap.

Is the scoring model based on real data?

Yes. A curated corpus of ~25 years of public marketing performance data (benchmarks from HubSpot, Ahrefs, SimilarWeb, Clutch, industry surveys, etc.) — with proprietary data layered on top.

Try it in 60 seconds

Paste any stat claim — we score it without asking you to sign up.