AI Commerce Validator

Free, no signup. Public discovery and merchant-feed readiness for agentic commerce. It does not attempt credentialed checkout.

Built by Patrick Stox

Baseline: local-baseline-2026-07-12 · 2026-07-12

Commerce protocol baseline last reviewed Jul 12, 2026.

Identity comparisons run only when discovery JSON supplies the matching feed_url (also feed.url or links.feed) or merchant_id (also merchant.id) value.
Commerce validation evidence

Next steps

Runs entirely in your browser — nothing you paste is uploaded or stored. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Ai Commerce Validator? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
Commerce truth comparator
Does the URL, visible selection, schema, feed and purchasable item describe the same product?
 
   
 
How to use it
 
  1. Paste a public ACP-style discovery response, a merchant feed, or both.
  2. Use XML with item/entry elements or TSV with a header row for the feed.
  3. Select Validate. Read each pass or warning independently and note any section marked not evaluated.
  4. Continue with live endpoint, schema, crawler-access, account, and checkout testing outside this offline check.
 
Example result Example data — engine calculation
 
The interactive example uses fictional example.com data and returns:
 
pass Valid JSON discovery response.
pass Public checkout/discovery endpoint declared.
pass Required merchant-feed values are present in at least one row.
pass Sampled product IDs are unique.
pass Sampled product image URLs are absolute HTTP(S) URLs.
pass Validated 1 sampled feed row.
Feed parser: tsv.
Product/Offer schema, llms.txt, AI-crawler access, and authenticated checkout are not evaluated.
 
What the results mean
 
Pass means the narrow local shape check succeeded. Warn means malformed JSON, no declared endpoint, no parsed rows, or a required value missing from the sample. Not evaluated is used for absent sections and adjacent checks outside this tool. A pass is not protocol certification.
 
How it works
 
The discovery validator parses JSON and looks for checkout_url, endpoint, or links.checkout. When you explicitly supply an expected feed URL or merchant identity, it compares that value with a corresponding discovery value. Missing values remain not evaluated; a mismatch is emitted only when both sides provide comparable evidence. The feed parser extracts up to 200 XML items/entries or TSV rows and runs deterministic shape checks.
 
Features
  • Discovery and merchant-feed checks can run together or independently.
  • Explicit XML, TSV, unknown-format, and not-evaluated states.
  • Real baseline freshness disclosure and browser-only parsing.
  • Interactive fictional example with no live commerce action.
 
Limitations
  • Field presence can be distributed across different rows; it is not a row-by-row completeness guarantee.
  • Feed URL and merchant comparisons assert string identity after conservative normalization; they do not prove ownership or that the URL is reachable.
  • No URL fetching, schema validation, feed-policy validation, authentication, cart, payment, tax, shipping, or order testing.
  • XML parsing supports a small tag set and is not a full namespace-aware feed parser.
  • Protocols evolve; use the displayed baseline date when interpreting results.
 
Frequently asked questions
What does the AI Commerce Validator check?
It checks whether pasted discovery contentURL discovery is how search engines find URLs to crawl — by pull (following links and reading sitemaps) and by push (you notify them via IndexNow, the Indexing API, or WebSub). It's the find step that comes before a page is ever fetched. is valid JSON and declares a public endpoint, and whether a pasted XML or TSV merchant feed contains required values, unique product IDs, and absolute HTTP(S) image URLs.
Does this validate a live ACP or UCP checkout?
No. The tool is an offline public-discovery and feed-shape check. It does not authenticate, add products to a cart, submit payment, or verify order lifecycle behavior.
Which merchant feed formats are supported?
It recognizes XML item or entry elements and tab-separated data with a header row. It samples at most 200 rows and does not support arbitrary CSV.
Does a passing feed result mean every product row is valid?
No. Required-field presence is checked across the sampled rows, and the result does not validate currencies, controlled availability values, URL reachability, product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two., or account policy.
Is my commerce data uploaded?
No. Discovery JSON and feed text are parsed locally in your browser.
 
 
People also explore
ToolEntity Coverage AnalyzerToolGoogle Knowledge Graph ExplorerToolVideo SEO CheckerArticleAI Commerce SEOArticleAI SearchArticleHow AI Search Works
 
 
 
Feature requests for Ai Commerce Validator
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
     
        
 
Common issues & how to fix them
 
     
  •  Error Commerce discovery file is invalid Fix: Publish valid JSON at the discovery location and declare a public checkout or discovery endpoint in the supported field. 
  •  Error Product feed item lacks a stable identifier Fix: Give every feed item a stable, unique product identifier that remains unchanged across feed refreshes. 
  •  Error Product title is missing Fix: Add a nonempty, product-specific title to every feed item rather than relying on a category or brand alone. 
  •  Error Product price is missing or invalid Fix: Supply a numeric product price in the feed’s expected format and pair it with a valid currency when required. 
  •  Error Product availability is missing or invalid Fix: Map each item to a supported availability value and keep it synchronized with the purchasable product page. 
  •  Error Product URL is missing or invalid Fix: Add a fully qualified, reachable canonical product URL for every feed item. 
  •  Warning Product image URL is missing or invalid Fix: Supply an absolute HTTP(S) product image URL for every affected feed row. 
  •  Error Product identifier is duplicated Fix: Give every product row one unique stable ID and merge or remove duplicate records. 
  •  Warning Discovery feed location conflicts with the expected feed Fix: Update the discovery feed URL or the expected merchant feed location so both values identify the same canonical feed, then validate again. 
    •