Turn a public AI product claim into evidence questions before you rely on it.

Before a buyer relies on a vendor's AI claim, paste the public URL, exact claim text, or both. Check AI Claims turns the wording into evidence requests, buyer questions, and safer wording for procurement and due diligence.

Review a public AI product claim See a sample Claim Receipt

Public AI product claims only Evidence questions, not true/false decisions, compliance verdicts, or vendor ratings Not legal advice

Claim Receipt

CR-2026-0605 example-vendor.com 2026-06-05

Evidence burden for this claim High

Claim reviewed

“Our AI achieves 98% accuracy and fully automates document review for any document type.”

Claim wording signal

Accuracy / Performance Automation / Replacement

Numeric accuracy claim combined with absolute automation wording, without a named benchmark, task scope, or human-review boundary.

Evidence to request

Benchmark name, test set, and evaluation date
Document types included and excluded
Human-review thresholds and escalation criteria

Buyer questions

Which document types were included in the 98% result?
Which cases still require human review?

Claim Receipt output

What the checker gives you.

A compact receipt you can use in vendor emails, procurement notes, or team review.

01 Receipt field

Evidence-burden note

Shows the claim type, the wording signal, and why the claim needs evidence before a buyer relies on it.

02 Receipt field

Evidence to ask for

Lists the benchmarks, documentation, scope limits, or review boundaries to request from the vendor.

03 Receipt field

Buyer questions and wording boundaries

Gives reusable follow-up questions and safer wording limits for procurement or due diligence notes.

Original claim stays attached

The reviewed sentence stays next to the evidence-burden note, so the receipt stays tied to the exact public wording.

Evidence burden stays visible

The receipt shows which wording pattern needs evidence and where source context may apply.

Follow-up language stays reusable

Buyer questions and wording boundaries are written for vendor emails, procurement notes, or team review.

Methodology

Start here

Have exact vendor wording

Use the checker. Paste the exact claim sentence, public AI product page URL, or both, then generate a Claim Receipt.

Open checker

Need context first?

02 Need claim type guidance Use the guides. Match wording to accuracy, automation, compliance, ROI, superlative, or vague AI-powered claim patterns. 03 Need a documented source example Use the case library. Read source-backed examples that connect a claim pattern to an evidence gap. 04 Need regulator source context Use the source matrix. Compare FTC, SEC, and ASA/CAP source context without treating it as a compliance database.

Common questions

Before you check a claim.

Is this legal advice or a compliance check?

No. The result is an evidence-burden note for public claim wording. It does not decide whether the claim is true or false, whether the product is legally acceptable or compliant, or whether a buyer should approve it.

Read the full disclaimer

What should I paste?

Paste a public AI product page URL, an exact AI product claim sentence, or both. Do not paste confidential material, contracts, security reports, PHI, PII, or internal vendor material.

Source-backed areas

Source-backed review areas.

AI washing examples Pattern library FTC AI claims Regulator briefing AI replacement claims Claim pattern AI detector accuracy claims Claim pattern

Cases

Official or high-confidence sources only. Use them as evidence context for buyer-side AI product claim review, not as accusation feeds.

Browse cases

Regulations

FTC, SEC, and ASA entry points for claim substantiation, accuracy, and outcome language. Source context only, not legal advice.

View sources

Pages publish as content is reviewed and sourced.