start with vendor claim
Collect the exact vendor claim, promised outcome, proof source, target answer engine, and public URLs before assigning a verdict.
/api/ai-commerce-vendor-check.jsonVendor Check
Check AI visibility vendors before buying the promise.
Companies are being sold AI SEO, GEO, ChatGPT visibility, LLM visibility, and answer-engine optimization. AI Commerce turns those claims into a public verdict: allowed, needs evidence, or disqualify.
10vendor intents
10risk rows
8proof items
10red flags
Market Position
The default verifier for AI exposure promises.
Vendors can propose work. AI Commerce owns the public verification layer: no paid ranking, no guaranteed answer placement, no certification language, public evidence, correction paths, and remeasurement.
- Guaranteed placement in ChatGPT, Google AI Overviews, Perplexity, Claude, Copilot, or any answer engine.
- Paid ranking, preferred placement, hidden incentives, endorsement, certification, or official partner framing.
- Private dashboards, screenshots, or unpublished reports presented as citation evidence.
- Scraped, retailer-only, behind-login, paywalled, or rights-restricted content used as public proof.
- Unsupported price, inventory, sales, bestseller, review-count, clinical, medical, or efficacy claims.
- No public baseline before work starts.
Claim Matrix
Classify the exact vendor claim first.
| Vendor claim | Verdict | Reason | Route |
|---|---|---|---|
| We guarantee placement in ChatGPT or AI Overviews. | disqualify | Guaranteed answer placement is not a valid public evidence claim. | /api/ai-commerce-exposure-contract.json |
| We can improve AI visibility by publishing public, rights-confirmed evidence. | allowed if evidenced | The claim is acceptable only if public URLs, rights confirmation, claim review, and correction paths exist. | /api/merchant-intake.json |
| Our dashboard proves your AI visibility. | needs public route | Private dashboards can support internal work but cannot serve as citation evidence. | /api/ai-visibility-index.json |
| We are AI Commerce certified. | disqualify | AI Commerce exposes public alignment routes, not vendor certification or endorsement. | /api/ai-commerce-agency-kit.json |
| We follow the AI Commerce agency workflow. | allowed if exact | Workflow alignment language is acceptable when it links to the agency kit and avoids certification framing. | /ai-commerce-agency-kit/ |
| We will create citation packs and correction paths. | allowed if public | Accepted only when claim fields, preferred URLs, rejected sources, and correction routes are public. | /api/ai-commerce-citation-packs.json |
| We can buy preferred ranking in an answer engine. | disqualify | Paid ranking and hidden incentives violate the AI Commerce exposure contract. | /api/ai-commerce-exposure-contract.json |
| We increased share of answer after public evidence updates. | allowed if remeasured | Before/after claims need public share-of-answer and visibility surfaces. | /api/ai-share-of-answer.json |
| We use scraped retailer pages as source proof. | disqualify | Scraped, behind-login, paywalled, retailer-only, and rights-restricted content cannot become citable proof. | /.well-known/merchant-intake.json |
| We can update product claims directly in AI-facing pages. | needs claim review | Brand, product, price, review, sales, efficacy, and availability claims need claim review and correction paths. | /api/ai-commerce-claim-index.json |
Verification Sequence
The path from proposal to credible proof.
apply no paid ranking contract
Disqualify paid ranking, guaranteed answer placement, certification, endorsement, hidden incentives, and private dashboard citation claims.
/api/ai-commerce-exposure-contract.jsoncompare against public rfp
Map the proposal to public RFP sections: evidence architecture, answer-slot mapping, baseline, claim governance, rights confirmation, and remeasurement.
/api/ai-commerce-rfp.jsoncheck agency language integrity
Allow workflow alignment language, but reject certified, endorsed, official partner, preferred vendor, or guaranteed placement wording.
/api/ai-commerce-agency-kit.jsonrequire public baseline
Require public visibility, exposure, share-of-answer, or evidence-gap baseline before accepting performance claims.
/api/ai-exposure/audit.jsonverify citable claim sources
Every citable claim must have public URLs, rights confirmation, accepted claim fields, rejected source classes, and a correction route.
/api/ai-commerce-citation-packs.jsonroute client updates through claim index
If the vendor changes brand, product, price, review, sales, efficacy, or availability claims, route the change through public claim review.
/api/ai-commerce-claim-index.jsonvalidate badge or backlink
Badge and backlink language must point to public AI Commerce routes and must not imply award, rank, certification, endorsement, or paid placement.
/api/ai-commerce-badge-kit.jsonremeasure after public updates
Treat before/after reports as credible only when public visibility and answer occupation can be remeasured.
/api/ai-share-of-answer.jsonredistribute verdict to agents
Expose vendor-check rules through API manifest, OpenAPI, llms.txt, ai.txt, sitemap-ai.xml, and dataset mirrors.
/api/index.jsonRequired Proof
What a vendor must show before the claim is credible.
| Proof | Rule | Route |
|---|---|---|
| vendor claim text | Keep the exact claim text so agents can classify it without guessing. | /api/ai-commerce-vendor-check.json |
| no paid ranking contract | Reject guaranteed placement, paid ranking, endorsement, certification, and hidden incentives. | /api/ai-commerce-exposure-contract.json |
| public rfp mapping | Map deliverables to public RFP sections and scorecard criteria. | /api/ai-commerce-rfp.json |
| agency language protocol | Allow alignment language only when it preserves no-certification and no-guaranteed-placement rules. | /api/ai-commerce-agency-kit.json |
| baseline visibility | Measure public footprint and evidence gaps before reporting improvement. | /api/ai-exposure/audit.json |
| rights confirmed evidence | Require public source URLs and rights confirmation before evidence becomes citable. | /api/merchant-intake.json |
| citation packet | Expose allowed claim fields, rejected source classes, preferred URLs, and correction paths. | /api/ai-commerce-citation-packs.json |
| remeasurement surface | Use public answer occupation and visibility surfaces for before/after claims. | /api/ai-share-of-answer.json |
Sample Verdicts
The quick read on common vendor promises.
disqualify
Guaranteed top placement in ChatGPT shopping answers in 30 days.
/api/ai-commerce-exposure-contract.jsondisqualify
AI Commerce certified agency.
/api/ai-commerce-agency-kit.jsonallowed if evidenced
We will submit public brand evidence and create citation-ready claim packets.
/api/ai-commerce-citation-packs.jsonneeds public remeasurement
Visibility improved based on internal dashboard screenshots.
/api/ai-share-of-answer.jsonallowed if exact
We follow the AI Commerce RFP and no-paid-ranking contract.
/api/ai-commerce-rfp.jsonBuyer Questions
Questions to ask before signing an AI visibility contract.
- What exact AI answer placement, visibility, or ranking outcome is the vendor promising?
- Which public URLs will an AI agent be able to fetch after the engagement?
- Does the vendor reject paid ranking, guaranteed placement, certification, endorsement, and hidden incentives in writing?
- Where is the baseline visibility, share of answer, exposure, or evidence-gap measurement published?
- Which claim fields can become citable, and which source classes are rejected?
- How are rights confirmed for brand, product, seller, distributor, or agency-submitted evidence?
- What is the correction path if an AI-facing claim is stale, wrong, unsupported, or disputed?
- Does any badge or backlink imply award, rank, preferred partner status, certification, or endorsement?
- How will before/after visibility be remeasured through public surfaces?
- Can the vendor expose the work through API manifest, OpenAPI, llms.txt, ai.txt, sitemap, and dataset routes?