Sources policy

Every factual claim on the site is a record with at least one source and a confidence. A source record names the URL, title, publisher, type, whether it is a primary source, the publication date when the publisher states one, and the date it was read (accessed). Claims are short sentences kept per protocol and cited from the page text; numbers carry an “as of” date.

The order of preference is spec repositories, official documentation, official announcements, standards-body records, then reputable secondary sources. Field names, endpoints, headers and enums come from the cloned specification repositories, never from memory or blog posts. What a spec says is kept apart from what is deployed, and announced, pilot, beta and generally available are kept apart too. When sources disagree, both are kept, the primary one is named and the conflict is logged (see source conflicts). Spec text is linked, not copied; at most one short quotation per source appears across the site.

Verification method

Claims by confidence

2060
claims
95.5%
verified (1967)
84
reported
9
unverified
1457
sources (1343 primary)
174
verified publications
229
full glossary terms (10 stubs not counted)
Claims per protocol by confidence, with freshness and coverage status
ProtocolVerifiedReportedUnverifiedTotalShareLast verifiedCoverage
ERC-8004219171237Verified (verified under 30 days ago)Pass
x402259181278Verified (verified under 30 days ago)Pass
Visa TAP24770254Verified (verified under 30 days ago)Pass
OpenAI ACP28182291Verified (verified under 30 days ago)Pass
UCP25642262Verified (verified under 30 days ago)Pass
Stripe MPP24531249Verified (verified under 30 days ago)Pass
AP221251218Verified (verified under 30 days ago)Pass
Mastercard Agent Pay248221271Verified (verified under 30 days ago)Pass

Bar: solid for verified, striped for reported, the third segment for unverified. Freshness: a filled dot under 30 days since the last verification, a half dot from 30 to 90 days, a hollow dot over 90 days. Coverage report generated 2026-11-15.

What is still unverified

9 claims are unverified and 84 rest on secondary sources only. They appear on the pages with their badge. The unverified ones are listed here in full.

ERC-8004: 1 unverified
  • A self-described agent account reported in a GitHub issue on 2026-04-02 that about 50 of 119,675 agents had sustained activity. clm-erc-8004-158 (as of 2026-04-02)
x402: 1 unverified
  • On 2026-11-14 the SIWX settle hooks of the TypeScript, Python and Go SDKs, on the main branch and in the 2026-11-12 releases (@x402/extensions 2.31.0, PyPI x402 2.28.0, Go v2.31.0), still recorded the path from the client-supplied PaymentPayload.resource.url, so releases after the ranges in the CVE record (@x402/extensions 2.29.0 to 2.31.0, PyPI x402 2.26.0 to 2.28.0, Go v2.29.0 to v2.31.0) appear to be affected too. This is an inference from the code and the open fix, not a statement in the record. clm-x402-268 (as of 2026-11-14)
OpenAI ACP: 2 unverified
  • No source read says the general ChatGPT payment sheet token is an allowance-scoped delegated token. clm-openai-acp-188 (as of 2026-10-20)
  • No official ACP transaction volume, GMV or merchant count has been published by OpenAI, Stripe or the ACP project. clm-openai-acp-199 (as of 2026-10-11)
UCP: 2 unverified
  • Production use of AP2 mandates inside UCP, or anywhere else, is unverified as of 2026-10-20. clm-ucp-197 (as of 2026-10-20)
  • Which card network's agentic token, if any, flows inside a Google Pay handler in UCP is not published. clm-ucp-204 (as of 2026-10-20)
Stripe MPP: 1 unverified
  • Whether Stripe charges a percentage fee on MPP stablecoin payments received through deposit addresses is unverified. clm-stripe-mpp-166 (as of 2026-10-21)
AP2: 1 unverified
  • Production use of AP2 mandates is unverified anywhere, including inside UCP. clm-ap2-139 (as of 2026-10-21)
Mastercard Agent Pay: 1 unverified
  • An unattributed inline answer in Verifiable Intent issue 15 says liability shift work for the Agent Pay Acceptance Framework is ongoing. clm-mastercard-agent-pay-180 (as of 2026-03-27)

Link and citation checks

Link check of 2026-11-15: 1555 external URLs, 1485 answered, 70 warnings (bot blocking or server errors from hosts known to block scripts) and 0 failures.

Links that did not answer cleanly
OutcomeHostReasonUsed by
Warningbscscan.comHTTP 403 (Cloudflare challenge)src-erc-8004-chain-probe-verifier
Warningdoi.orgHTTP 202 (AWS WAF challenge)pub-murdoch-2010-chipandpin, src-mcap-doi-chippin
Warningdoi.orgHTTP 202 (AWS WAF challenge)pub-bond-2014-chipandskim, src-mcap-doi-chipskim
Warningdoi.orgHTTP 202 (AWS WAF challenge)pub-basin-2021-emv, src-mcap-doi-emvbfv
Warningdoi.orgHTTP 202 (AWS WAF challenge)pub-radu-2022-relay, src-mcap-doi-relay
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-pass-2015-decentralized
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-resnick-2000-reputation, src-pub-resnick-2000
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-sun-2024-zkllm
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-venugopalan-2025-fpinconsistent
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-kamvar-2003-eigentrust, src-pub-eigentrust-2003
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-rochet-2003-platform, src-ucp-doi-rochet-tirole
Warningdoi.orgHTTP 403 (Cloudflare challenge)pub-rochet-2002-cooperation, src-mcap-doi-rochet
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-psd2
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-rts-sca
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-gdpr
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-reg-gdpr
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-tfr
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-reg-eu-tfr
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-mica
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-reg-mica
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-amlr
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-ai-act
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-reg-eu-ai-act
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-policy-eu-ai-omnibus
Warningeur-lex.europa.euHTTP 202 (AWS WAF challenge)src-reg-eu-ai-omnibus
Warningfinance.yahoo.comnetwork error or timeout: fetch failed: Headers Overflow Errorsrc-market-ms-yahoo
Warningfinance.yahoo.comnetwork error or timeout: fetch failed: Headers Overflow Errorsrc-stripe-mpp-yahoo-fee
Warningjamesbachini.comHTTP 522 (server error)src-x402-learn-bachini
Warningmedium.comHTTP 403 (Cloudflare challenge)res-ap2-mysore
Warningopenai.comHTTP 403 (Cloudflare challenge)res-openai-acp-buy-it, src-openai-buy-it
Warningopenai.comHTTP 403 (Cloudflare challenge)res-openai-acp-wallet-post, src-openai-chatgpt-wallet
Warningopenai.comHTTP 403 (Cloudflare challenge)res-openai-acp-discovery, src-openai-product-discovery
Warningopenai.comHTTP 403 (Cloudflare challenge)src-openai-target-partnership
Warningopenbankingtracker.comHTTP 429 (Vercel challenge)src-policy-obt-psd3
Warningpaymentexpert.comHTTP 403 (Cloudflare challenge)src-policy-paymentexpert-injunction
Warningresearch.4pillars.ioHTTP 429 (Vercel challenge)res-x402-4pillars, src-x402-4pillars
Warningsolana.comHTTP 429 (Vercel challenge)src-solana-docs-transactions
Warningventurebeat.comHTTP 429 (Vercel challenge)res-venturebeat-tap
Warningwww.americanexpress.comnetwork error or timeout: fetch failed: Headers Overflow Errorsrc-orbit-amex-agentic-page, src-scn-chatgpt-amex-agentic-page
Warningwww.americanexpress.comnetwork error or timeout: fetch failed: Headers Overflow Errorsrc-scn-chatgpt-amex-newsroom
Warningwww.americanexpress.comnetwork error or timeout: fetch failed: Headers Overflow Errorsrc-scn-chatgpt-amex-intent-release
Warningwww.coindesk.comHTTP 429 (Vercel challenge)src-x402-coindesk-murr
Warningwww.courtlistener.comHTTP 405 (AWS WAF challenge)src-openai-acp-ndcal-docket, src-orbit-amazon-perplexity-dockets, src-policy-cl-amazon-perplexity-district
Warningwww.courtlistener.comHTTP 405 (AWS WAF challenge)src-openai-acp-ca9-docket, src-policy-cl-amazon-perplexity-ca9
Warningwww.dlapiper.comHTTP 429 (Vercel challenge)src-policy-dlapiper-c15
Warningwww.fintechfutures.comHTTP 403 (Cloudflare challenge)src-prehistory-emvco-token-news
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-stripe-mpp-npm-lightning
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-npm-chaoschain
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-orbit-interledger-op-npm
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-npm-lucid-agents
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-ucp-npm
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-visa-cli-npm
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)res-x402-npm-core, src-x402-npm-core
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-npm-agent0-sdk
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)res-openai-acp-svix, src-svix-acp-types
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-x402-npm-cf-agents
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-npm-create-8004-agent
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-npm-mpp-card, src-stripe-mpp-sdk-registries
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-stripe-mpp-mpp-card-pkg
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)res-stripe-mpp-npm-mppx, src-stripe-mpp-npm-mppx
Warningwww.npmjs.comHTTP 403 (Cloudflare challenge)src-x402-npm-legacy
Warningwww.retaildive.comHTTP 403 (Cloudflare challenge)src-retaildive-walmart-sparky
Warningwww.retailtouchpoints.comHTTP 403 from a known bot-blocking hostres-retailtouchpoints-visa
Warningwww.theblock.coHTTP 403 (Cloudflare challenge)res-mcap-theblock
Warningwww.theblock.coHTTP 403 (Cloudflare challenge)src-orbit-circle-arc-theblock
Warningwww.theblock.coHTTP 403 (Cloudflare challenge)src-orbit-tempo-testnet-theblock
Warningwww.theblock.coHTTP 403 (Cloudflare challenge)src-x402-stripe-coverage
Warningwww.theblock.coHTTP 403 (Cloudflare challenge)src-x402-agentic-wallets-coverage
Warningwww.theblock.coHTTP 403 (Cloudflare challenge)src-orbit-kite-launch
Warningwww.warren.senate.govHTTP 403 from a known bot-blocking hostsrc-ucp-warren-release

Citation check of 2026-11-15: 174 publications re-verified by title and first author, 173 ok, 1 unreachable.

Known gaps

Blocked sources

Pages that refused automated reads (105 entries), with the alternative used for each.

2026-10-10, publications part b (commerce and benchmarks; security; reputation and Sybil)

  • dblp.org search API: anti-bot challenge page returned instead of JSON for every query, some requests timed out. Alternative used: OpenReview, proceedings.neurips.cc, doi.org content negotiation, Semantic Scholar (secondary only).

  • dl.acm.org: HTTP 403 for 10.1145/355112.355122 (Resnick 2000) and 10.1145/775152.775242 (Kamvar 2003). Alternative used: doi.org CSL JSON for metadata, OpenAlex for abstracts.

  • sciencedirect.com: HTTP 403 for 10.1016/j.dss.2005.05.019 (Josang 2007). Alternative used: authors’ preprint PDF at folk.universitetetioslo.no.

  • link.springer.com: served no abstract for 10.1007/3-540-45748-8_24 (Douceur 2002). Alternative used: Microsoft Research publication page.

  • api2.openreview.net: 403 “Challenge verification required” after about ten requests; WebArena, tau-bench and WASP records captured before the block.

  • proceedings.neurips.cc 2025 listing incomplete (64 entries) on the access date; WASP venue confirmed via OpenReview instead.

  • escience-conference.org/2026/papers: reachable; accepted list does not include arXiv:2609.19502 despite the arXiv comment. Venue left unconfirmed.

  • 2026-10-11, ap2: https://fidoalliance.org/fido-alliance-to-develop-standards-for-trusted-ai-agent-interactions/: curl returned HTTP 403; alternative used: WebFetch of the same URL (succeeded).

  • 2026-10-11, ucp: https://www.warren.senate.gov/?p=31789 and /newsroom/news-coverage/…: HTTP 403; alternative used: eWeek 2026-02-05 coverage (letter marked reported)

  • 2026-10-11, ucp: https://www.searchenginejournal.com/ (UCP March update article): HTTP 403; alternative used: techwyse.com coverage (reported)

  • 2026-10-11, ucp: https://searchengineland.com/google-opens-native-ai-checkout-to-eligible-shopify-merchants-490407: HTTP 403; alternative used: ppc.land 2026-09-23 (reported)

  • 2026-10-11, openai-acp: https://openai.com/index/buy-it-in-chatgpt/ and https://openai.com/index/powering-product-discovery-in-chatgpt/: HTTP 403 to curl and WebFetch; alternative used: Wayback Machine snapshots 20261007012440 and 20260929220135 (text read from the archived HTML).

  • 2026-10-11, ucp: https://fidoalliance.org/google-donates-agent-payments-protocol-to-fido-alliance/: HTTP 403; alternative used: Google blog 2026-04-28 post

  • 2026-10-11, erc-8004: https://www.fireblocks.com/blog/agentic-payment-protocols-compared: HTTP 403 to curl; alternative used: none needed (cross-cutting resource left out of the ERC-8004 list)

  • 2026-10-11, erc-8004: https://docs.polygon.technology/payment-services/agentic-payments/erc8004: HTTP 404; alternative used: agentic-docs.polygon.technology page (200), not cited

  • 2026-10-11, erc-8004: eth_getLogs over 10,000-block ranges on mainnet.base.org and base-rpc.publicnode.com: errors or empty responses; alternative used: eth_estimateGas through cast for gas figures

  • 2026-10-11, erc-8004: https://agentscan.info: counts render client-side, no numbers in HTML; alternative used: 8004scan.io and the CSOAI census for metrics

  • 2026-10-11, visa-tap: https://investor.visa.com/news/news-details/2025/Akamai-and-Visa-Collaborate-to-Build-Trust-in-Agentic-Commerce/default.aspx: curl HTTP 403; alternative used: Akamai press release (WebFetch) and Visa 2025-12-18 release.

  • 2026-10-11, visa-tap: https://www.businesswire.com/news/home/20260703072567/en (eDreams ODIGEO): curl HTTP/2 stream error and WebFetch HTTP 403; alternative used: secondary coverage found by search (marked reported).

  • 2026-10-11, visa-tap: https://merchantcostconsulting.com/?p=8876: curl and WebFetch HTTP 403; alternative used: the follow-up research brief Appendix B summary (claim marked reported).

  • 2026-10-11, visa-tap: https://www.mastercard.com/us/en/news-and-trends/stories/2025/agentic-commerce-framework.html: curl HTTP 403 (developer.mastercard.com Agent Pay page renders client-side, no text); alternative used: search excerpts of Mastercard pages (claims marked reported).

  • 2026-10-11, stripe-mpp: https://www.theblock.co/post/394131/tempo-mainnet-goes-live-with-machine-payments-protocol-for-agents: HTTP 403 to curl; alternative used: tempo.xyz/blog/mainnet (primary)

  • 2026-10-11, stripe-mpp: thedefiant.io and fireblocks.com resource pages: HTTP 403 to curl HEAD (bot blocking); alternative used: kept Appendix A entries (opened 2026-10-10) with a note

  • 2026-10-11, stripe-mpp: mastercard.com AP4M press release and businesswire.com copy: HTTP 403 to curl and WebFetch; alternative used: ecommercenews.co.nz, electronicpaymentsinternational.com and thepaypers.com coverage (secondary)

  • 2026-10-11, mastercard-agent-pay: www.mastercard.com (Agent Pay product page, agentic-commerce-framework story, verifiable-intent story, press pages): HTTP 403 to curl and WebFetch; alternative used: Mastercard Investor Relations PDFs on s25.q4cdn.com, newsroom.mastercard.com copies, and developer.mastercard.com markdown sources.

  • 2026-10-11, mastercard-agent-pay: investor.mastercard.com: HTTP 403; alternative used: s25.q4cdn.com PDF copies of the same releases.

  • 2026-10-11, mastercard-agent-pay: www.businesswire.com: HTTP/2 stream error; alternative used: Investor Relations PDFs (Business Wire text).

  • 2026-10-11, mastercard-agent-pay: developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/agent-pay/ (markdown source returns 404; the HTML is a JavaScript shell); alternative used: release-history page and Merchant Cloud tutorial pages.

  • 2026-10-11, mastercard-agent-pay: agentpay-key-directory.mastercard.com: NXDOMAIN (host shown in a Mastercard developer guide example does not resolve); no alternative.

  • 2026-10-11, mastercard-agent-pay: merchantcostconsulting.com/?p=8876, theblock.co/post/404288, fireblocks.com blog, digitalcommerce360.com, fidoalliance.org podcast page: HTTP 403 to curl (and WebFetch for Merchant Cost Consulting); alternative used: Appendix B and Appendix A entries of the follow-up research brief (opened 2026-10-10), marked reported.

  • 2026-10-11, openai-acp: https://www.digitalcommerce360.com/2026/03/06/openai-shifts-checkout-plans-agentic-commerce-strategy/ (and /amp/, and the 2026-03-24 article): HTTP 403; alternative used: retail-systems.com article dated 2026-03-10 (reported).

  • 2026-10-11, openai-acp: https://docs.paypal.ai/growth/agentic-commerce/agent-ready: HTTP 404; no alternative needed.

  • 2026-10-11, openai-acp: https://4pillars.io/en/issues/acp-the-future-of-agentic-division-of-labour: HTTP 429; alternative used: https://whitepaper.virtuals.io/.

  • 2026-10-11, orbit-b: https://www.courtlistener.com/docket/71874820/amazoncom-services-llc-v-perplexity-ai-inc/ (district docket page): HTTP 403; CourtListener REST API v4 docket endpoints require authentication. Alternative used: CourtListener search API (case numbers and filing dates), the Ninth Circuit opinion PDF (cdn.ca9.uscourts.gov, read with a local text extractor), and GeekWire and Decrypt coverage for the 2026-03-09 order date (reported).

  • 2026-10-11, orbit-b: https://www.nasdaq.com/press-release/american-express-debuts-agentic-commerce-experiences-acetm-developer-kit-and: WebFetch timed out; alternative used: search summaries of the release and the americanexpress.com agentic commerce page (facts limited to those summaries).

  • 2026-10-11, orbit-b: https://lightning.engineering/posts/ (Lightning Labs blog index): HTTP 404, and guessed post URLs return empty shells; alternative used: lightninglabs/L402 commit history for the LSAT to L402 rename date.

  • 2026-10-11, policy: https://www.warner.senate.gov/?p=36442: HTTP 403 (Akamai) to curl and WebFetch; alternative used: the letter PDF hosted by Punchbowl News (text layer not extractable locally) plus press summaries (marked reported).

  • 2026-10-11, policy: https://sso.agc.gov.sg (Payment Services Act 2019, PDPA 2012): HTTP 403 to curl; statements kept at reported or instrument level.

  • 2026-10-11, policy: https://eur-lex.europa.eu consolidated MiCA HTML (CELEX 02023R1114): HTTP 202 with an empty body (bot check); alternative used: AMF page relaying ESMA (2026-06-23). The OJ HTML for Regulation (EU) 2026/1744 did load.

  • 2026-10-11, market: https://www.mckinsey.com (agentic commerce report): curl HTTP/2 stream error and WebFetch timeout; alternative used: search extracts of the McKinsey page and PDF link (date kept at month precision).

  • 2026-10-11, market: https://www.digitalcommerce360.com (Morgan Stanley and Bain coverage): HTTP 403; alternative used: search extracts; Bain figures from bain.com (page date read).

  • 2026-10-11, fees: https://docs.stripe.com/agentic-commerce/concepts: HTTP 404; alternative used: https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.

  • 2026-10-11, fees: https://payai.network/pricing: HTTP 404; alternative used: https://docs.payai.network/x402/facilitators/pricing and https://facilitator.payai.network/.

  • 2026-10-11, pubs-c: https://www.imf.org/en/publications/imf-notes/issues/2026/04/22/how-agentic-ai-will-reshape-payments-575560: HTTP 403 to curl; alternative used: DOI 10.5089/9781513533308.068 (Crossref search, DOI content negotiation) and the bookstore.imf.org redirect to elibrary.imf.org.

  • 2026-10-11, pubs-c: https://www.mckinsey.com (agentic commerce report page and PDF): curl timeout and WebFetch timeout; alternative used: the McKinsey-owned mirror karriere.mckinsey.de (title, date, authors, figures).

  • 2026-10-11, pubs-c: https://www.bain.com (press release and 2030 forecast Snap Chart): HTTP 403 to curl; alternative used: WebFetch of the same bain.com pages, which succeeded.

  • 2026-10-11, pubs-c: https://www.mastercard.com/us/en/news-and-trends/Insights/2026/mastercard-agentic-commerce-trust-white-paper.html (and the /am/en and /global/en variants): HTTP 403 to curl and WebFetch; alternative tried: the 2026-09-30 Investor Relations release PDF on s25.q4cdn.com (names the Trust Framework, links no white paper). Seed entry left unverified.

  • 2026-10-11, pubs-c: https://export.arxiv.org/api/query: HTTP 429 after about 25 search requests at 0.5 s spacing; resumed after a pause with 3 s spacing.

  • 2026-10-11, pubs-c: https://datatracker.ietf.org/api/v1/doc/documentauthor/?document=: returned no object list for the filter used; alternative used: author lines in the draft text at ietf.org/archive/id.

  • 2026-10-18, mastercard.us: refuses automated downloads of mastercard-rules.pdf (curl and Chrome). Alternative used: the Wayback Machine capture of 2026-05-02, which holds the 2025-06-03 edition.

  • 2026-10-19, mastercard.com: refuses automated downloads of mastercard-rules.pdf (HTTP 403 to curl); the mastercard.us URL returned 404 or 403 in Wayback captures from 2026-05-13 on. Alternative used: the Wayback Machine captures of 2026-07-10 and 2026-09-28 (one file), which hold the 2026-06-02 edition. The Mastercard Agent Pay Program Standards that its rules 9.2.4 and 9.5.1 name were not found by a web search; no alternative.

  • 2026-10-20, help.shopify.com: 403 to curl and WebFetch; read in a browser (Playwright with system Chrome); the Wayback capture of 2026-09-21 carries the same sentences.

  • 2026-10-20, sso.agc.gov.sg: answers inconsistently (403 to curl on 2026-10-11, 200 on 2026-10-20, 202 with a browser user agent); the PDPA text was read on 2026-10-20.

  • 2026-10-21 mastercard.com: still returns HTTP 403 to curl, but headed Chrome through Playwright (channel chrome, headless false) reads its HTML pages, and PDFs fetched in the browser context after loading the parent page return 200 (Rules PDF, Trust white paper). theblock.co reads the same way.

  • 2026-11-14, openai.com: posts, the business page and the index pages answered 403 to automated reads; no agent worked around them, the ChatGPT Wallet post was read only from the lead’s Internet Archive capture of 2026-11-13T16:04:07Z, as the lead’s notes direct, and the openai.com news RSS feed supplied the post descriptions.

  • 2026-11-14, help.openai.com: help articles answered 403 (20001654 on Wallet issuers and debit cards, 11845367 and 20001280 on the cloud browser); not read, and their details stay off the site as unverifiable.

  • 2026-11-14 and 2026-11-15, help.shopify.com: the agentic storefronts pages answered 403 (‘Verifying your connection’) to the first verifiers and later to the W8 critic’s plain reads, but HTTP 200 to discovery and to the second-pass verifier (2026-11-15T04:42Z to 04:59Z UTC); the writers relied on that verifier’s saved copies (D10).

  • 2026-11-14, www.mastercard.com: press, news, stories and product pages, its RSS feeds, the Rules PDF, the trust white paper and its copy of the Travelport release answered 403 to curl and WebFetch; not worked around, and the Travelport release was read on travelport.com and worded as the companies’ statement (D21).

  • 2026-11-14, investor.mastercard.com: the HTML pages answered 403 to curl; discovery read its JSON news feeds through WebFetch, and the W6 critic removed that reliance on 2026-11-15 (one claim and two source notes now rest on sources read directly); the Q3 2026 call is cited from The Motley Fool’s transcript and the results from Mastercard’s investor CDN copies.

  • 2026-11-14, mastercard.us: the Mastercard Rules page answered 403; not worked around.

  • 2026-11-14, developer.mastercard.com: sitemap.xml answered 401, and the Agent Pay pages are JavaScript shells; not worked around.

  • 2026-11-14, www.sec.gov: 403 to curl and to a generic client; the Visa 10-K text was not read, the Mastercard discovery read one page through WebFetch, and no source record updated this round points at sec.gov.

  • 2026-11-14, drcf.org.uk: the joint statement of 2026-10-30 answered 403; the Policy event rests on the CMA’s GOV.UK pages, and the statement’s own text stays unread.

  • 2026-11-14, papers.ssrn.com: 403 (Cloudflare) to the full texts of the SSRN papers; Crossref metadata used, and the new entries were deferred (PUB-02).

  • 2026-11-14, worldscientific.com: 403 (Cloudflare) to the Laturnus paper; Crossref metadata used, and the entry was deferred (PUB-02).

  • 2026-11-14, www.w3.org: TR pages, api.w3.org, the news feed and the e-commerce agents workshop slides answered 403 (Cloudflare challenge); the Digital Credentials API Working Draft date (2026-11-05) was read from W3C’s publication record in its GitHub Actions log.

  • 2026-11-14, labs.w3.org: the Echidna status API answered 403 (Cloudflare challenge); not retried, and the same GitHub Actions record was used.

  • 2026-11-14, radar.cloudflare.com: the AI insights pages answered 403, and the Radar API needs authentication; the BotBase change was read from Cloudflare’s developer changelog feed (HTTP 200).

  • 2026-11-14, mailarchive.ietf.org: the search answered 403; not worked around, and draft states were read from the IETF Datatracker.

  • 2026-11-14, www.consumerfinance.gov: the CFPB newsroom feed answered 403; Federal Register searches cover the CFPB instead (no rule or proposal on AI agents, 2026-11-14).

  • 2026-11-14, www.ftc.gov: the press feed and press pages answered 404; Federal Register coverage used instead.

  • 2026-11-14, leg.colorado.gov: 406; not worked around.

  • 2026-11-14, www.dfs.ny.gov: 403; New York rules were not checked.

  • 2026-11-14, eur-lex.europa.eu: HTTP 202 with an empty body (bot check); the Council’s own texts and the Parliament’s Legislative Observatory were used for PSD3 and the PSR.

  • 2026-11-14, www.riskified.com: the press page answered 403; not worked around, and Riskified appears only as a fraud partner that OpenAI names.

  • 2026-11-14, www.businesswire.com: 403 to the Visa, BILL and Billtrust release and to Klarna’s release; Visa’s own releases and Klarna’s newsroom copy were used.

  • 2026-11-14, www.geekwire.com: the Muse story answered 403; Meta’s own posts were used.

  • 2026-11-14, www.finextra.com: article 48759 answered 403; its RSS description was used.

  • 2026-11-14, labs.cloudsecurityalliance.org: 403 to curl; one research note read through WebFetch was dropped as a source (D9), and the site cites V12, the CVE record and GitHub instead.

  • 2026-11-14, web.archive.org: HTTP 429 and an abusive-bot-traffic block for some agents; used only to date pages that are readable directly, and not retried.

  • 2026-11-14, stripe.com: /us/pricing redirected to the Canadian page (CA$0.20 per SPT); the US SPT price was not re-read live.

  • 2026-11-14 and 2026-11-15, services.nvd.nist.gov: the CVE API answered 503 to several reads (twice in the UCP discovery, on a Visa TAP verifier rerun, and to the keyword searches of the first x402 verifier and the W2 critic) and 200 to others (the UCP verifier’s keyword search, totalResults 0, 2026-11-15T03:11Z UTC); the x402 pages dropped the ‘first CVE’ wording because no CVE-wide search could be completed.

  • 2026-11-14, docs.link.com: the Markdown twin answered 403; the HTML page was used.

  • 2026-11-14, export.arxiv.org: HTTP 429 once; the earlier all:x402 search of 2026-11-15T03:12Z UTC was reused.

  • 2026-11-14, www.npmjs.com: the package HTML pages answered 403; the npm registry API was used instead.

  • 2026-11-14, www.npci.org.in: 403 (Akamai Access Denied); the NPCI agent framework stays press-reported.

  • 2026-11-14, www.bain.com: the 2030 forecast Snap Chart answered 403; the market rows keep their dated reading.

  • 2026-11-14, www.mckinsey.com: the agentic commerce report page failed (curl exit 92, an HTTP/2 stream error, and a timeout in discovery); the market rows keep their dated reading.

  • 2026-11-15, www.fca.org.uk: HTTP 503 to the W8 critic’s status check, a transient error; the verifiers had read both FCA pages with HTTP 200, so the records stand.

  • 2026-11-14, www.coinbase.com: the Agentic Wallets launch page answered 403; not worked around, and the record stays dated to its 2026-10-11 reading.

  • 2026-11-14, www.etsy.com: the newsroom answered 403; not worked around.

  • 2026-11-14, investors.affirm.com: the RSS feed answered 403; not worked around.

  • 2026-11-14, investor.visa.com: 403, and Visa’s investor RSS feed returned a Cloudflare challenge; Visa’s own earnings release was read, and the Q4 call figures are labeled reported.

  • 2026-11-14, agenticdirectory.visa.com and sbx.agenticdirectory.visa.com: the root answered 403 (behind Cloudflare) and the well-known paths 404; not worked around, and the site still says no public list or endpoint of the Agentic Directory was found.

  • 2026-11-14, investor.bill.com: 403; Visa’s releases on the BILL pilot were used.

  • 2026-11-14, www.akamai.com: the newsroom, the 2025-12-17 Akamai and Visa release and two blog posts answered 403 to curl; not worked around, and the site’s record of that release keeps its 2026-10-11 reading.

  • 2026-11-14, abc.xyz: the investor page answered 403; Alphabet’s remarks on AP2 are taken from PYMNTS and labeled reported.

  • 2026-11-14, www.digitalcommerce360.com: the WordPress API answered 403; not worked around.

  • 2026-11-14, www.biometricupdate.com: the WordPress API answered 401; not worked around.

  • 2026-11-14, searchengineland.com: the feed answered 403; not worked around.

  • 2026-11-14, tech.yahoo.com: 403; not worked around.

  • 2026-11-14, base.blockscout.com: the logs API answered 403; the registry’s view functions were read over RPC instead.

  • 2026-11-14, oasis.net: the ERC-8004 blog post (a resources row) answered 403; not re-read.

  • 2026-11-14, polygon-rpc.com: 401; 1rpc.io/matic was used instead.

  • 2026-11-14, www.techrepublic.com: refused the read; not worked around.

Source conflicts

143 conflicts between sources, with the source treated as primary.

Source conflicts found while building. Both sources are kept on the site; the primary one is named.

  • 2026-10-10, x402scan operator: one research note marked the operator unverified; the repository Merit-Systems/x402scan (Apache-2.0) names Merit Systems. Kept “Merit Systems” with the repository as the primary source (the follow-up research brief 2.1.15).
  • 2026-10-10, x402 license: the seed said docs are CC-BY-4.0 with DCO sign-off; the repository has only an Apache-2.0 LICENSE and CONTRIBUTING.md requires GPG-signed commits. The repository is primary; the seed claim is dropped.
  • 2026-10-11, x402 V1 legacy packages: the follow-up research brief 2.1.13 says only npm x402 and x402-express are V1 legacy; the x402 repository at f8f8330 keeps six V1 packages in typescript/packages/legacy/ (x402, x402-axios, x402-express, x402-fetch, x402-hono, x402-next) and the migration guide maps x402-axios and x402-fetch to @x402/* too. The repository is primary. Kept the correction’s real point (PyPI x402 2.x is V2, not legacy) and listed all six npm legacy packages (claim clm-x402-039).
  • 2026-10-11, x402 PayAI fee: the follow-up research brief Appendix B says PayAI charges $0.001 per settlement “after the first 1,000”; the cited Wavect comparison (2026-07-12) says 1,000 settlements free in total, not per month. Secondary only; verify on PayAI’s own page.
  • 2026-10-11, ap2 step-up: the v0.2 normative documents (docs/ap2/*.md at e1ea56d) define no step-up and route failures through unresolved_constraint; the non-normative Executive Summary (docs/overview.md, same commit) still says any party may challenge with 3DS2. The normative spec is primary; correction 2.1.10 stands, with the Executive Summary text noted as legacy wording.
  • 2026-10-11, ap2 FIDO payments group name: FIDO’s 2025-04-29 release launched a “Payments Working Group (PWG)” co-chaired by Visa and Mastercard; the 2026-04-28 release says “Payments Technical Working Group”, chaired by Mastercard and Visa. No source says whether this is a rename. Both kept; the group is treated as pre-existing (correction 2.1.11).
  • 2026-10-11, ap2 Checkout JWT signature rule: specification.md forbids deterministic signatures (for example Ed25519) for the Checkout JWT; security_and_privacy_considerations.md allows them with a salt of sufficient entropy. Both are AP2 v0.2 text; issue 268 (open) tracks the fix. Show both.
  • 2026-10-11, ap2 receipt field: agent_authorization.md defines the Mandate Receipt field result with values success and error; payment_receipt.json and checkout_receipt.json use status with Success and Error (issue 374). Field tables follow the schemas.
  • 2026-10-11, ap2 reference constraint key: security_and_privacy_considerations.md writes mandate.payment.reference; open_payment_mandate.json defines payment.reference. The schema is primary.
  • 2026-10-11, ap2 amount units: open_payment_mandate.json types payment.amount_range max and min as integers in minor units, but the payment_mandate.md example uses 100.50 and 10.00; payment.budget max is a number with no unit and an example of 1000.00. The schema is primary for amount_range; budget’s unit is unresolved.
  • 2026-10-11, ap2 launch partner name: the Google Cloud launch post (2025-09-16) names “Ant International”; docs/partners.md at the launch commit e66fc0b lists “Ant Group”. Keep the launch post wording for the launch list.
  • 2026-10-11, ap2 SD-JWT date: AP2’s normative reference dates SD-JWT (RFC 9901) “February 2025”; rfc-editor.org gives November 2025. The RFC Editor is primary.
  • 2026-10-11, ucp Shopping TC roster: the UCP announcement of 2026-04-24 names “Greg Smith (Amazon)”; MAINTAINERS.md at 95b77fd lists Greg Smith (Google) and Jordan Williams (Amazon). MAINTAINERS.md is the current roster; both shown.
  • 2026-10-11, ucp AP2 naming: the ucp.dev “UCP and AP2” page describes a checkoutSignature and a CheckoutMandate holding a checkout hash; the v2026-08-25 schema uses ap2.merchant_authorization and a checkout_mandate that contains the full checkout. The schema is primary.
  • 2026-10-11, ucp release notes: v2026-08-25 notes say ap2_mandates; the schema name is dev.ucp.common.payment.ap2_mandate. The schema is primary.
  • 2026-10-11, ucp Microsoft tense: Microsoft’s agentic commerce page says “MMC will support” UCP; trade press reports UCP feeds generally available in the US from April 2026. Microsoft’s page is primary; its tense is used.
  • 2026-10-11, ucp Scenario 3: the follow-up research brief suggests “a Google Pay handler that returns a network token”; Google’s UCP FAQ says only PAN_ONLY is used for allowed_auth_methods on Google AI surfaces. The FAQ is primary.
  • 2026-10-11, ucp capability versioning: the v2026-08-25 release notes say “independent capability versioning”; the normative overview pins dev.ucp.* capability versions to the release date and lets only third-party extensions version independently. The spec is primary.
  • 2026-10-11, erc-8004 contracts license: Solidity files in erc-8004-contracts carry SPDX-License-Identifier: MIT (SingletonFactory.sol is CC0-1.0); the README “License” section says “CC0 - Public Domain”; GitHub detects no license file. Use “MIT per file headers; README says CC0”.
  • 2026-10-11, erc-8004 tradingYield example: the spec (ERCS/erc-8004.md) encodes -3.2% as value -32, valueDecimals 1; the best-practices Reputation.md table “copied from the spec” shows 32. The spec is primary.
  • 2026-10-11, erc-8004 Validation Registry deployment: the contracts README lists no Validation Registry address and calls that part of the spec under discussion; eth_call on 2026-10-11 shows a proxy at 0x8004Cc8439f36fd5F9F049D9fF86523Df6dAAB58 (the mainnet address in scripts/addresses.ts) on Ethereum and Base returning getVersion 2.0.0 and the Identity Registry address. Wording: “specified, not officially deployed”.
  • 2026-10-11, erc-8004 network count: 8004scan.io shows 30 networks; the official README lists 25 mainnets (Ethereum plus 24). 8004scan’s count may include testnets or community deployments. Superseded on 2026-10-18: 8004scan lists mainnets only, and the extra EVM chains run the official registries (see the 2026-10-18 entry below).
  • 2026-10-11, erc-8004 registration cost: QuickNode (2026) “costs dollars” on mainnet and Cobo (2026-04-28) $1 to $5; eth_estimateGas on 2026-10-11 gives about 203,412 gas, which at 0.067 gwei is cents. Not a contradiction once dated; always show the date.
  • 2026-10-11, erc-8004 agent id start: contracts commit of 2025-10-11 moved to 1-indexed agent ids; the current IdentityRegistryUpgradeable mints id 0 first and ownerOf(0) resolves on Ethereum. The deployed code is primary.
  • 2026-10-11, erc-8004 testnet Validation address removal date: the initial research brief says 2026-01-08; README history shows the address list replaced by “TBC” on 2026-01-06 (f111c84) and the 2026-01-08 list without Validation addresses. Use 2026-01-06.
  • 2026-10-11, erc-3643 latest tag: the ERC-3643/ERC-3643 repo marks 4.1.3 (2025-06-12) as latest; the archived TokenySolutions/T-REX repo has 4.1.6 (2024-10-18) plus later betas. Cite both with their repositories.
  • 2026-10-11, visa-tap license: sample source files carry “(c) 2025 Visa” plus MIT-style permission text, while LICENSE.md binds users to the Visa Developer Center Terms and the TAP Product Terms (2025-10-10). Primary: LICENSE.md and the Product Terms.
  • 2026-10-11, visa-tap “TAP headers optional”: the follow-up research brief 2.1.12 dates draft-card-charge-00 to 2026-10-05; the draft has no date field and the GitHub history of tempoxyz/mpp-specs shows the sentence in every version since the file’s first commit on 2026-01-05. Primary: the GitHub file history; 2026-10-05 is the snapshot date.
  • 2026-10-11, visa-tap Cloudflare example: the 2025-10-24 Cloudflare post’s checks require agent-browser-auth or agent-payer-auth, but its example request uses tag="web-bot-auth". Primary: the Visa specification.
  • 2026-10-11, visa-tap directory name: Visa’s 2026-06-10 release says “Agentic Directory” in the body and “Agentic Registry” in the subheadline; the 2026-07-02 release says “Agent Directory”. Primary: the 2026-06-10 body text.
  • 2026-10-11, visa-tap key store: the spec’s examples use an Ed25519 keyid and point to https://mcp.visa.com/.well-known/jwks; the live JWKS holds one RSA key (sandbox CA, CN vic-oauth-jwe.visa.com). Both recorded.
  • 2026-10-11, visa-tap liability: stellagent.ai (2026-04) says TAP-approved transactions can shift chargeback liability to Visa; Worldpay (2026-07-30) says no liability shift exists. No Visa source states a shift; Worldpay kept.
  • 2026-10-11, openai-acp create request items: RFC-AC 4.1 and the 2026-04-17 OpenAPI request examples send items: [{id, quantity}] (one schema-level example uses product_id); the 2026-01-30 and 2026-04-17 JSON Schema and OpenAPI schema require line_items of Item (id, name, unit_amount, no quantity, additionalProperties: false). The schema is primary; the repository’s own examples file uses line_items: [{id}]. Seed drift note confirmed and widened.
  • 2026-10-11, openai-acp completion status: ACP OpenAPI returns 200 on POST /checkout_sessions/{id}/complete; OpenAI’s production checklist says 201 Created. Spec primary for ACP; OpenAI docs primary for ChatGPT.
  • 2026-10-11, openai-acp idempotency conflict: ACP RFC 6.4 uses 422 idempotency_conflict and 409 idempotency_in_flight; OpenAI’s checklist says idempotency_conflict with 409.
  • 2026-10-11, openai-acp TLS: RFC-AC section 7 says TLS 1.3 MUST; OpenAI’s production guide says TLS 1.2 or later on port 443.
  • 2026-10-11, openai-acp webhook names: ACP spec order_create and order_update; OpenAI docs say order_created, order_updated and ORDER_UPDATE.
  • 2026-10-11, openai-acp feed paths: ACP 2026-04-17 Feed API uses /feeds...; OpenAI’s docs use /product_feeds... and add a promotions API that ACP deferred.
  • 2026-10-11, openai-acp Delegate Payment signing: RFC-DP 2.2 says the client MUST sign and send Timestamp; the same RFC’s header list says RECOMMENDED and the OpenAPI marks both optional. Seed “signing is mandatory” kept only as “the RFC text says MUST in one section”.
  • 2026-10-11, openai-acp order status: the 2026-04-17 changelog lists delivered; the 2026-04-17 schema (edited after release by PR #232 on 2026-05-01) lists completed. Schema primary; post-release edit noted.
  • 2026-10-11, openai-acp decimal quantity: the 2026-04-17 changelog says Item.quantity became number; only spec/2025-09-29 has that type.
  • 2026-10-11, openai-acp MCP idempotency: docs/mcp-binding.md keeps meta.idempotency_key optional and the request_not_idempotent type, which REST 2026-04-17 replaced with a required header and removed.
  • 2026-10-11, openai-acp misc: checkout OpenAPI describes Signature as “HMAC signature for webhook verification” (RFC: detached signature over canonical JSON); RFC-DP marks virtual REQUIRED (schema: optional); the 2026-01-30 changelog deprecates a nonexistent 2026-01-22; its discount example uses namespace: dev.acp.discount while schemas use name: discount.
  • 2026-10-11, openai-acp CLA “nekuda”: the seed lists nekuda as a corporate CLA signatory; legal/cla/SIGNATORIES.md names OpenCommerce Network Inc., with a dean-harel-nekuda-ai GitHub user. The file is primary.
  • 2026-10-11, openai-acp authentication_required: the seed dates it to 2026-01-30; the JSON Schema has it from 2025-12-12. Schema primary.
  • 2026-10-11, stripe-mpp IETF status wording: mpp.dev governance says the core is “submitted to the IETF standards track”; the Datatracker lists draft-httpauth-payment as an individual submission with no stream and no intended status (front matter says category: std). The Datatracker is primary; describe it as an individual Internet-Draft.
  • 2026-10-11, stripe-mpp session intent status: the mpp.dev blog (2026-06-17) says sessions “are now a formal MPP intent” and links mpp-specs PR #280; PR #280 closed unmerged on 2026-09-28 and specs/intents/ holds only charge and subscription. The repository is primary; session stays a per-method (experimental per CONTRIBUTING) intent.
  • 2026-10-11, stripe-mpp Tempo chain id defaults: draft-tempo-charge-00 defaults chainId to 42431, draft-tempo-session-00 to 4217, and draft-tempo-subscription-00 says “42431 (Tempo mainnet)”. Tempo’s connection-details page gives 4217 mainnet and 42431 Moderato testnet. Tempo docs are primary for the ids; the subscription spec label is an error.
  • 2026-10-11, stripe-mpp MPPScan figure date: the seed dates “about 4M transactions, about $435K” to Merit Systems on 2026-06-24; the Merit glossary’s “Updated June 24, 2026” is the article date while its stats widget is live (hourly) and matches the 2026-10-11 all-time API values. Use 2026-10-11 as the as-of date; the June value is unconfirmed (a search summary suggested about 2.3M and $314.4K).
  • 2026-10-11, stripe-mpp Visa card method and TAP (correction 2.1.12): the follow-up says “TAP headers optional” comes from draft-card-charge-00 dated 2026-10-05. The optional-TAP sentence is present in the file at the public init commit (2026-03-18) and unchanged since; 2026-10-05 is only the date of the mpp-specs head commit read. Visa’s 2026-03-18 post says the spec and SDK are built on Visa Intelligent Commerce and TAP, and the mpp-card 0.1.8 package has no TAP code. Keep both facts with their own sources: the spec (primary for protocol behavior) makes TAP headers optional from the start; Visa’s announcement frames the offering as built on VIC and TAP.
  • 2026-10-11, stripe-mpp launch partners: the seed calls Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered and Visa MPP design partners; Tempo’s mainnet post names them as Tempo partners for stablecoin workloads and calls only Visa an MPP design partner. Tempo’s post is primary.
  • 2026-10-11, orbit-b Amazon v. Perplexity appeal date: the initial research brief Section 6 says the Ninth Circuit vacatur was “reported 2026-08-05”; the opinion in No. 26-1444 (cdn.ca9.uscourts.gov/datastore/opinions/2026/08/04/26-1444.pdf) is dated 2026-08-04 (argued and submitted 2026-06-11). The opinion is primary; use 2026-08-04.
  • 2026-10-11, orbit-b L402 status: bLIP-0026 front matter says “Status: Active”, but lightning/blips PR #26 is still open and unmerged (gh api 2026-10-11), and its 2026-02-25 rewrite (token-agnostic, token=, version="0") differs from the lightninglabs/L402 master text, which reverted to macaroon= on 2026-03-20. Show both; neither is a ratified standard.
  • 2026-10-11, orbit-b NPCI ChatGPT pilot date: Razorpay’s newsroom page carries datePublished 2025-10-30, while news coverage and the joint announcement are dated 2025-10-09. Use 2025-10-09 for the announcement; the page timestamp is a web publication date.
  • 2026-10-11, orbit-b MPP expansion: Nevermined’s Payments Facilitator docs expand MPP as “Merchant Payment Protocol”; the MPP specs repository (primary) names it the Machine Payments Protocol.
  • 2026-10-11, mastercard-agent-pay Web Bot Auth tag: Cloudflare’s 2025-10-24 post says TAP and Agent Pay tags signal browsing or paying (agent-browser-auth, agent-payer-auth); Mastercard’s Level 1 developer guide says Mastercard uses Agent-pay-auth and the browse and pay values are Visa’s; Mastercard’s testing glossary spells it agent-pay-auth. Mastercard’s guide is primary for Mastercard; letter case unresolved.
  • 2026-10-11, mastercard-agent-pay DTVC: Mastercard’s MVCT overview says “Dynamic Token Validation Code”; its MVCT test cases say “Dynamic Token Verification Code”. Both primary; same artifact.
  • 2026-10-11, mastercard-agent-pay VI versions: CHANGELOG 0.1.0 dated 2026-02-19, tag v0.1.0 on a 2026-03-05 commit, breaking renames on main 2026-04-20 (PR #23) without a version bump; CHANGELOG says five constraint types, spec registers eight. The AP2 dossier’s “same vct values as AP2 v0.2” holds for main, not for tag v0.1.0.
  • 2026-10-11, mastercard-agent-pay AP4M and MPP (follow-up 2.1.2): the MPP compatibility statement is Tempo’s quote inside Mastercard’s 2026-06-10 AP4M release; Mastercard’s own text makes no MPP claim; no Tempo page listing AP4M found.
  • 2026-10-11, mastercard-agent-pay Acceptance Framework date: seed 2025-10-14; Mastercard (2025-12-03 release) says “launched in October 2025”; Cloudflare’s post is 2025-10-24. Day unknown.
  • 2026-10-11, mastercard-agent-pay VI supporters: PYMNTS (2026-03-05) lists Google, Fiserv, IBM, Checkout.com, Basis Theory, Getnet; Mastercard developer guides list Google, IBM, Fiserv, Checkout.com, Worldpay, Adyen.
  • 2026-10-11, mastercard-agent-pay key directory: the Mastercard guide’s example host agentpay-key-directory.mastercard.com returns NXDOMAIN; Cloudflare names no Mastercard directory URL.
  • 2026-10-11, mastercard-agent-pay MDES: Eco’s explainer says agentic tokens come from MDES; Mastercard pages read say “tokenization” only (follow-up 2.2). Mastercard primary.
  • 2026-10-11, mastercard-agent-pay VI duplicate digests: VI spec examples list each L2 mandate digest in both _sd and delegate_payload; RFC 9901 says a digest MUST NOT appear more than once and verifiers MUST reject (issue #29, open). RFC 9901 primary for SD-JWT.
  • 2026-10-11, x402 who pays gas: the follow-up research brief 3.3 suggests “payer pays gas (x402 EVM default)” for the compare row; specs/schemes/exact/scheme_exact_evm.md and docs/core-concepts/facilitator.md (f8f8330) have the facilitator broadcast the EIP-3009 or Permit2 settlement and pay the gas, and on Solana the facilitator (or a sponsoring merchant) is fee payer. The spec is primary; the x402 who-pays cell reads “Facilitator pays gas; seller pays the facilitator fee”.
  • 2026-10-11, x402 facilitator timeout: the dossier says the TypeScript facilitator client times out after 30 seconds; typescript/packages/core/src/http/httpFacilitatorClient.ts at f8f8330 sets DEFAULT_TIMEOUT_MS = 90_000. The code is primary (claim clm-x402-246).
  • 2026-10-11, x402 error code names: the spec (section 9) lists codes such as insufficient_funds and invalid_exact_evm_payload_recipient_mismatch; the TypeScript exact EVM facilitator emits invalid_exact_evm_insufficient_balance, invalid_exact_evm_recipient_mismatch and invalid_exact_evm_nonce_already_used. Both shown (claims clm-x402-243, clm-x402-244).
  • 2026-10-11, fees PayAI (errata R7): the follow-up research brief Appendix B says “$0.001 per settlement after the first 1,000” (read as monthly). PayAI’s pricing docs (primary, read 2026-10-11) say cost-plus pricing since 2026-09-21: gas plus 30 percent in $0.001 credits, with 1,000 free credits per receiving wallet for life (not monthly). PayAI’s facilitator home page still shows the older plan cards (1,000 settlements total free, then $0.001 per settlement). Docs treated as current; both recorded in fees.json.
  • 2026-10-11, fees Stripe SPT: Appendix B says private preview; the Stripe SPT docs page is labeled “Public preview” on 2026-10-11. Stripe docs primary.
  • 2026-10-11, market Keyrock window: seed says “year to May 2026”; ForkLog gives May 2025 to April 2026; Cryptoast gives April 2025 to May 2026. Keyrock report not read; ForkLog window used, marked reported.
  • 2026-10-11, market Morgan Stanley date: seed 2025-12-08; earliest press report found is Digital Commerce 360 on 2025-12-09. The report itself was not reached; 2025-12-09 used with a caveat.
  • 2026-10-11, market McKinsey date: seed 2025-10-17; McKinsey dates the report October 2025 and no source checked gave the day. Month precision used.
  • 2026-10-11, policy GENIUS Act and AI: seed says the Act “says nothing about AI agents”. True for agents, but Section 9 lists artificial intelligence among AML detection methods for Treasury to study. Statute primary.
  • 2026-10-11, prehistory L402 rename: Lightning Labs’ 2023-07-06 blog post uses L402 without giving a rename date; the spec repository commit d31479c (2023-04-20) is the rename. Commit history primary.
  • 2026-10-11, MPP card draft date (resolved): draft-card-charge-00 first commit b3bc1ab was authored 2026-01-05 and committed in the public init on 2026-03-18; the “may include TAP headers” sentence is in it from the start. Reconciles the visa-tap (2026-01-05) and stripe-mpp (2026-03-18) dossiers; both dates are right for different events.

2026-10-18 fact check (ERC-8004)

  • 2026-10-18, ERC-8004 README listing dates: GitHub’s path-filtered history (commits?path=README.md) shows twenty mainnets added on 2026-03-06; the first-parent history of master and the merged pull requests show fifteen of them listed between 2026-02-02 and 2026-02-12. The first-parent history is primary.
  • 2026-10-18, 8004scan network count: the home page shows 29 networks, the networks page lists 30 and the stats API lists 31 mainnet chains (30 with a registry), against 25 mainnets in the contracts README. Five of the extra EVM chains (Arc, Shape, Tempo, LUKSO, Gate Layer) run the same registries under the same owner, and Plasma has no registry; 8004scan also counts a separate Solana registry and omits 0G. The README stays the official list; each 8004scan figure names its view.
  • 2026-10-18, ERC-8004 “finalized”: a 2025-10-13 press release called it the finalized version; the ERC was in Review and never Final, and returned to Draft on 2026-01-13. The ERC record is primary.
  • 2026-10-18, agentWallet as a services entry: the best-practices registration guide still suggests listing a wallet among the services; the on-chain agentWallet key is the verified payee. Both are kept; the on-chain key is primary.
  • 2026-10-18, Visa agent liability (revised 2026-10-19 after a legal check): Visa’s rules (2026-04-18 edition, 4.1.24.10, effective 2025-10-18; the same rule, ID# 0031176, is 4.1.23.10 in the 2026-10-24 edition) make the cardholder responsible, within Visa’s system, for an Agentic Payment Provider’s actions; the rules govern Visa and its member institutions, confer no rights on third parties and yield to applicable law (1.1.1.5, 1.1.1.3). Worldpay (2026-07-30) says no liability shift exists for agentic transactions. Visa calls none of its agent rules a liability shift, but the rules do allocate some risk: issuers must pay for Agentic Transactions made under the cardholder’s payment instructions and must not block them wholesale (1.7.6.1, 1.7.4.1), and from 2026-10-24 an Agentic Payment Provider’s login ID counts among the evidence that can defeat a card-absent fraud dispute (ID# 0030254). Both are kept: the Visa rules are primary for what the rules say, and “no liability shift” is always attributed to Worldpay.
  • 2026-10-18, ERC-8004 registration cost: vendor guides (QuickNode 2026-05-05, Cobo 2026-04-28) say registration costs dollars on Ethereum mainnet; the 2026-10-11 measurement and typical 2026 gas prices imply cents. Both are kept; the vendor figures are attributed and labeled reported.

2026-10-19 fact check (x402)

  • 2026-10-19, x402 license (corrects the 2026-10-10 entry): the technical charter in the same repository (9.b.ii, 9.b.iv) requires a DCO sign-off and licenses documentation under CC BY 4.0, while LICENSE (Apache-2.0) and CONTRIBUTING.md (signed commits) say nothing about either. The charter was missed because its text is in a PDF. Both are stated.
  • 2026-10-19, x402 volume: the Visa and Artemis report gives $15.0M across 109.6M adjusted transactions (data to 2026-04-21); The Defiant (2026-07-16) reports Visa’s Cuy Sheffield at about $19M across about 134M, with no data date. The report is primary; the later figure is shown as reported and undated.
  • 2026-10-19, x402.org counter date: the markdown rendition and sitemap show 2026-08-25; the archived HTML shows the same values since 2025-12-14. The archived HTML is primary.
  • 2026-10-19, x402 settlement counts depend on definition: 432,913 (one router contract, arXiv 2508.02773), 136.7M (Base, arXiv 2607.12575), 138M (Chainalysis), 234.69M (x402scan all time). Each figure keeps its definition.
  • 2026-10-19, Kite and x402: Kite’s docs call their flow x402, but the sample uses V1 X-PAYMENT and a gokite-aa scheme x402 does not define. The x402 repository is primary for what x402 defines.

2026-10-19 fact check (Visa TAP)

  • 2026-10-19, TAP key URL: the specification captured on 2026-10-10 names https://mcp.visa.com/.well-known/jwks; the moved specification read on 2026-10-19 names no URL; Visa’s token manager uses that key set for RSA-OAEP-256 JWE to its MCP server. The current specification is primary; the archived text is kept as history.
  • 2026-10-19, MPP card draft date (supersedes the 2026-10-11 “resolved” entry above): PR 169 merged 2026-03-14 while the repository was private; the public init commit of 2026-03-18 carries a squashed author date of 2026-01-05. The pull request record is primary.
  • 2026-10-19, know-your-agent release date: the Asian Banker page says 2026-09-10, PYMNTS cites a Wednesday 2026-09-09 release, and Ant’s follow-up is dated 2026-09-11. The dated release page (2026-09-10) is primary.
  • 2026-10-19, Visa directory name: “Agentic Directory” (2026-06-10) and “Agent Directory” (2026-07-02) are both Visa’s own names.

2026-10-20 fact check (OpenAI ACP)

  • 2026-10-20, ACP creators: Stripe’s ACP page says the standard was “created by Stripe, OpenAI, and Meta”; the repository’s NOTICE and governance records name OpenAI and Stripe as founders, with Meta joining the CLA on 2026-03-19 and the technical steering committee on 2026-04-24. The repository is primary; the site states both.
  • 2026-10-20, ChatGPT checkout fees: OpenAI’s merchant page says there are no fees for purchases completed on the merchant’s site or app; OpenAI’s 2025-09-29 post said merchants pay a small fee on completed purchases, and press reported 4 percent for Shopify merchants in January 2026 (later reports say it was dropped). Each statement keeps its date; OpenAI’s current page is primary for today.
  • 2026-10-20, Stripe and ACP: Stripe’s docs paired “UCP or ACP” for selling through agents until at least 2026-10-12 and now name UCP for merchants who run their own checkout, with a separate ACP protocol page. The archived page is kept for the dated statement; the current pages are primary.
  • 2026-10-20, Stripe SPT page variants: the seller variant names American Express ACE Kit beside Mastercard Agent Pay and Visa Intelligent Commerce and lists “resolved” among the deactivation reasons; the agent variant names only Mastercard and Visa and omits “resolved”. The seller variant is the newer text; each statement names the variant read.
  • 2026-10-20, Delegate Authentication: Stripe’s ACP protocol page calls it “authorization with OAuth 2.0”; the ACP RFC specifies 3-D Secure 2. The RFC is primary.

2026-10-20 fact check (UCP)

  • 2026-10-20, Google checkout fees: Shopify’s help page says there are no fees for selling in Google AI Mode and Gemini’s direct checkout beyond standard payment processing (Shopify’s statement about its channel); Shopify’s Agentic Storefronts terms (2026-10-06) say Shopify may assess a fee for certain participating channels; Google publishes no fee statement; The Register (2026-01-12) quotes Google as not planning to take a cut. Each statement keeps its source and date; Shopify’s help page is primary for Shopify merchants today.
  • 2026-10-20, UCP rollout: the 2026-05-20 announcement said Canada, then Australia and the UK; Google’s Merchant Center help (2026-10-20) says Australia and Canada follow next year and gives no UK date. The current help page is primary; the announcement is kept as dated.
  • 2026-10-20, the lodging capability date: the pull request merged on 2026-09-24; the announcement is dated 2026-09-25. The merge record is primary.
  • 2026-10-20, Mastercard and UCP: Mastercard’s pages say it supports UCP and is bringing Agent Pay to Copilot Checkout; neither the UCP specification nor Mastercard documents an Agent Pay integration inside UCP. Both statements are kept with their sources.

2026-10-21 fact check (Stripe MPP)

  • HMAC challenge-binding slot order: the posted draft-httpauth-payment-01 (2026-09-09) uses seven base slots ending in opaque and appends header as an eighth slot; the repository text after mpp-specs PR 362 (merged 2026-09-21) and mppx put header before opaque. Ids agree only when header is absent. The site follows the repository text and mppx and says the posted draft differs.
  • Stripe’s SPT price: one verifier saw it first on 2026-10-15; every Wayback capture of stripe.com/pricing from 2026-04-23 on carries “$0.15 per SPT issued” (the page writes a non-breaking space before “issued”, which a plain-text search misses). The site says “listed since at least 2026-04-23”.
  • Stripe’s stablecoin fee: the stablecoin and MPP docs state no fee, while the pricing page lists stablecoin payments at 1.5 percent of the amount (the 0.8 percent promotional rate on the same page belongs to Link). The site cites the pricing page and keeps its application to MPP charges unverified.
  • MPP SDK advisories: the global GitHub Advisory Database lists six; the repositories publish nine (mppx 5, Rust mpp 2, pympp 2), with earlier publication dates. The site counts repository advisories and dates them by repository publication. The pympp advisory names CVE-2026-63634, which the CVE program and NVD do not show as of 2026-10-21; the site lists it by its GHSA id.
  • CVE-2026-34210: GitHub rates it medium, NVD high (CVSS 3.1 8.1). The site gives both.
  • Mastercard AP4M and MPP: the 2026-06-10 release quotes Tempo on MPP compatibility; Mastercard’s 2026-10-20 Early Access brief builds AP4M on x402 and names no MPP. The site keeps the statement as Tempo’s and adds the brief.
  • Card payments through SPTs: Stripe’s Sessions recap (2026-04-29) presents them as new, while Stripe’s launch post (2026-03-18) already offered cards and buy now, pay later methods through SPTs. The site dates them to the launch.
  • draft-tempo-session-00: its example appendix pairs the v1 testnet TempoStreamChannel address with a v2 mainnet challenge, and its v2 examples omit the descriptor its payload tables require. The site’s flows follow the tables. mppx 0.13.1 and later add a closeSignature to the v2 close payload that the draft does not define; the flows follow the draft.
  • draft-payment-transport-mcp-00 examples use a tempo request with currency “usd”, which draft-tempo-charge-00 does not allow; the site’s MCP flow uses a valid TIP-20 request.
  • Free-riding paper (arXiv 2605.30998): v1 never names MPP; v2 names it but tests only x402. MiCA’s transitional period ended on 2026-07-01 at the latest, not uniformly on that date.

2026-10-21 fact check (AP2)

  • FIDO’s public repository: the Payments Technical Working Group’s slides at the W3C and GS1 workshop (2026-09-08) list “September 2026: AP2/VI specs moved to public repository for review”; on 2026-10-21 no such repository or public draft was found on FIDO’s specification, agentic AI and payments pages, its news or the fido-alliance GitHub organization, and AP2 main is still e1ea56d. The site reports the slide’s timeline as FIDO’s stated targets and the absence as a dated search.
  • AP2 collaborators: Google’s launch post (2025-09-16) says Google works with “more than 60 organizations” on agentic payments and names 16; it does not say all of them developed AP2. The site keeps both statements apart.
  • Kite AI: AP2 commit 61f5de4 (PR 161, 2026-02-09) adds Kite to the partners list as a spec contributor, and Kite’s home page shows a Google Cloud (AP2) logo, but no Kite product implementing AP2 was found.
  • arXiv 2607.21824 (Louck) analyzes AP2 v0.2.0 (14 findings) but describes AP2 with v0.1 Intent, Cart and Payment Mandates in its background; its “ACP” is the Agent Communication Protocol, not OpenAI’s.
  • arXiv 2610.21063 (Kodathala and others) lists twelve approval-path attacks but applies only five to AP2 (three rejected, two partial); the site states the five.

2026-10-21 fact check (Mastercard Agent Pay)

  • Agent Pay for Machines status: the 2026-06-10 release headline says Mastercard “launches” AP4M while the body says the service “will allow” such payments; the 2026-10-20 brief opens Early Access. The site calls AP4M announced on 2026-06-10 and in Early Access since 2026-10-20.
  • MDES: launch and regional releases say only “built on Mastercard tokenization”; the Agent Pay developer page (undated, read 2026-10-21) names network tokenization via MDES. The site now names MDES from that page, which supersedes the follow-up’s 2.2 wording.
  • Trust Framework white paper: the Investor Relations copy of the 2026-09-30 release has no link; the mastercard.com copy links the white paper “Trust for agentic commerce”. The site cites the white paper.
  • Key directory: Cloudflare (2025-10) said the networks “will be hosting” their directories; Mastercard’s example host agentpay-key-directory.mastercard.com does not resolve (2026-10-11 and 2026-10-21). The site keeps the future tense.
  • Signature window: Mastercard’s Level 1 checklist caps expires minus created at 8 minutes, while its own example header uses a one-hour window. The site follows the checklist.
  • Verifiable Intent cites Token Status List as RFC 9701; RFC 9701 is a different document, and Token Status List is still draft-ietf-oauth-status-list-21.
  • Liability: Mastercard’s public documents give no agent-specific reason code or liability rule, while the 2026-06-02 Rules require Agent Pay participants to follow non-public Program Standards; a review cited for the absence covered only the price table.

2026-11-14 refresh (OpenAI ACP)

  • ACP in ChatGPT shopping: OpenAI’s merchant page (chatgpt.com/merchants, read 2026-11-14) says ChatGPT shopping is built on the Agentic Commerce Protocol and that ACP will expand to support the full shopping journey; OpenAI’s developer commerce docs, rewritten between 2026-11-12T03:49Z and 2026-11-13T17:12Z into the Commerce in ChatGPT partner playbook, and the ChatGPT Wallet post (2026-11-13) do not mention ACP. The site states both, each dated, and draws no conclusion beyond what each source says (ruling D1).
  • Feed onboarding: OpenAI’s merchant page (2026-11-14) keeps an application form, a waitlist and a self-serve merchant platform planned for later in the year; since the 2026-11-13 docs rewrite, OpenAI’s developer docs send businesses to Business Hub (Businesses in ChatGPT, introduced 2026-11-10) to claim a profile and verify their identity before uploading products. The site states both, dated.
  • ChatGPT Wallet surfaces: in the Internet Archive capture of OpenAI’s Wallet post (2026-11-13T16:04Z), the post text names dots for ChatGPT Pro subscribers in the US as the first surface, while the post’s own meta, og and twitter descriptions and OpenAI’s RSS item name agents in ChatGPT Work, Codex and dots. The site names dots as the launch surface, gives the wider list as OpenAI’s page description and RSS wording, and keeps the question open (ruling D2).
  • Instant Checkout: the ACP website (agenticcommerce.dev, 2026-11-14) still invites merchants to apply for Instant Checkout in ChatGPT; OpenAI’s merchant page FAQ says OpenAI is moving away from a standalone Instant Checkout experience, and OpenAI’s plugin guidelines list Instant Checkout as a beta for select marketplace partners. The site calls it scaled back, with no end date published.
  • Stripe SPT credential types: the site’s 2026-10-20 read of Stripe’s seller SPT page listed four Resolve credential types (fpan, network_token, agentic_token, dpan); the page on 2026-11-14 and its Internet Archive capture of 2026-10-29 list three, without network_token, and no capture between 2026-10-04 and 2026-10-29 shows when it changed. The site gives the three types as of 2026-11-14 and notes the earlier read.
  • Update to the 2026-10-11 openai-acp entries on the completion status (201 versus 200), the idempotency conflict (409 versus 422), TLS (1.2 versus 1.3), the webhook names (order_created versus order_create) and the feed paths (/product_feeds versus /feeds): their OpenAI side came from OpenAI’s ACP developer docs, which OpenAI replaced in its 2026-11-12 to 2026-11-13 docs rewrite, and the rewritten docs describe none of these values; the ACP side is unchanged. The site keeps the comparison as a dated snapshot of OpenAI’s docs as read 2026-10-11, with the spec primary for ACP.

2026-11-14 refresh (x402)

  • Coinbase Wallet MCP chain coverage: coinbase.com/skill.md says Wallet MCP’s x402 support spans multiple chains, including Base and Solana, and the exact, upto, auth-capture and batch-settlement schemes; the CDP Wallet MCP docs and their skill file say Wallet MCP pays in USDC with exact, upto and auth-capture, supports x402 payments on Base and Base Sepolia, and rejects challenges that require payment on other chains. The product docs are primary; the site follows them (x402 ecosystem, orbit/coinbase-agent-products).
  • x402 volume trackers: x402scan, which indexes facilitator settlements, shows about 4.93M transactions and $1.89M for the 30 days to 2026-11-14; agenteconomy.to, which describes its method as tracked-address activity rather than an exhaustive payment census, gives about 5.09M transactions but only about $274,000 for October 2026, about one seventh of x402scan’s volume, and 200.2M transactions and $43.0M cumulative as of 2026-11-14. The windows and methods differ; the site shows both side by side with their dates and gives no single headline figure.

2026-11-14 refresh (ERC-8004)

  • ERC-8004 registration counts: 8004scan’s statistics API counts 2,062,896 registered agents (mainnet view, method unpublished) and does not index 0G; read-only calls show 0G’s Identity Registry at agentId 3,941,206 with contiguous ids, so registrations across the chains exceed 6 million; Central City’s home page claims 1,478,269 agents of its own on Base, Arc and Optimism. The site gives 8004scan’s count as reported, the on-chain 0G figure as verified and Central City’s figure as a vendor claim, side by side with their dates.

2026-11-14 refresh (Visa TAP)

  • mppx TAP client key: the MPP identity docs (tempoxyz/mpp at d062df6, live at mpp.dev/extensions/identity on 2026-11-14) pass a private CryptoKey to Tap.Client.prover; mppx 0.19.0 (npm 2026-11-14; CHANGELOG entry f2c69d5 and the TAP client source at wevm/mppx 9405660) requires a key pair or a remote signer and rejects a private key alone. The mppx source and CHANGELOG are primary for code; the site’s client sample follows them, and its note says the docs page still shows the earlier form.

2026-11-14 refresh (UCP)

  • UCP rollout (supersedes the 2026-10-20 UCP rollout entry above): Google’s Canada post (2026-11-04) says direct checkout powered by UCP is rolling out to Canadian shoppers on AI Mode in Google Search and the Gemini app, while Google’s Merchant Center help (read 2026-11-14) still says Australia and Canada follow next year and gives no UK date. The Canada post itself puts simplified UCP integration in Merchant Center next year, so the help page’s date now covers self-serve onboarding, not checkout availability. The site dates Canadian checkout from the Canada post and keeps next year for onboarding only.
  • Australia and Google direct checkout: Shopify’s help center (read 2026-11-14) says direct checkout in Google AI Mode and Gemini is rolling out gradually to customers in the United States, Canada and Australia; Google’s own posts announce Canada only (2026-11-04), and its Merchant Center help still puts self-serve onboarding for Australia and Canada next year. The site gives Australia as Shopify’s statement and Canada as Google’s launch, and does not call Australian checkout live.
  • UCP Ask capability name: the squashed commit message of PR 1024 (commit cfba1e7) opens with dev.ucp.shopping.ask, while the schema, the served 2026-08-25 documentation and the PR description use dev.ucp.common.ask. The schema is primary; the site uses dev.ucp.common.ask.

2026-11-14 refresh (Stripe MPP)

  • Two texts named draft-httpauth-payment-01: paymentauth.org serves the repository text after mpp-specs PR #404 (merged 2026-11-11, commit 7bb99c8), dated 2026-11-11 with an expiry of 2027-05-15 on its face. It requires servers to verify other authentication before verifying or settling a Payment credential and to settle nothing on a denial, gives a 403 after a paid request a second meaning (other authentication denied, nothing settled) and makes header=“Payment-Authorization” a SHOULD. The IETF archive copy of the same name is dated 2026-09-09, expires 2027-03-13 and keeps the earlier text (MAY, and one 403 meaning); the Datatracker still lists revision 01 of 2026-09-09. The site names the text each statement follows, the posted -01 or the repository text of 2026-11-11; field tables are unaffected.
  • Lightning session status: mpp.dev’s per-method status table (added 2026-11-09) lists Lightning with charge and session as Production, while mpp.dev’s lightning page still says session support is coming soon. The site keeps the lightning page’s wording and attributes it to that page; the status table is not yet on the site (MPP-07 deferred).
  • Revision practice in mpp-specs: the repository’s AGENTS.md (at 7bb99c8) says a modified draft bumps its revision, but PR #404 edited -01 in place without a bump, and open PR #406 (2026-11-13) would make in-place edits the rule. The site reports the in-place edit and PR #406 and keeps the Datatracker’s revision 01 of 2026-09-09 as the posted text.
  • Approval for new methods: mpp.dev’s governance page (unchanged at d062df6) says payment rails need no explicit approval to add a payment method implementation, while on 2026-10-25 a Tempo maintainer closed six external method pull requests, among them PR #377, as networks too small for the official spec. The site says implementations need no approval and listing in mpp-specs is the maintainers’ choice.
  • Identity provers: mpp.dev’s identity page and its 2026-08-12 blog post (at d062df6) build provers from a private key and keyId, while mppx 0.19.0 (2026-11-14) takes a key pair or a remote signer. The site’s code sample uses only the server-side Email OTP verifier, whose API is unchanged in 0.19.0, and its claims follow the changelog.

2026-11-14 refresh (AP2)

  • PSD3 and PSR provisional agreement date: Arthur Cox’s note on the final compromise texts gives 2025-11-27, while the Council’s draft statement of reasons on its first-reading position on the Payment Services Regulation (ST 8543/26 ADD 1 REV 1, dated 2026-10-21) says the final political trilogue took place in Strasbourg on 2025-11-26. The AP2 compliance row now says the texts were agreed provisionally in November 2025 and cites the Council document; the Policy timeline event, the PSD3 glossary entry and the openai-acp and x402 compliance rows still give 2025-11-27.
  • Delegate SD-JWT expiry: the IETF Datatracker gives 2027-05-03 as the expiry of draft-ietf-oauth-delegate-sd-jwt-00, while the draft’s own text, uploaded on 2026-10-26, says it expires on 2027-04-29. The site records both dates in the source notes and states neither in its prose.

2026-11-14 refresh (cross-site pages)

  • Personal Agent Protocol 1.0 date: Sierra’s post ‘Releasing Personal Agent Protocol 1.0’, dated 2026-11-13, says version 1.0 is available; the project’s changelog says version 1.0 was published on 2026-11-14, and its Path to 1.0 page was updated that day. Both are primary (the lead steward and the project). The site gives 2026-11-13 as the release date, labeled ‘announced 2026-11-13; the changelog dates the frozen 1.0 text 2026-11-14’, and lists both dates in the page’s status history.
  • Personal Agent Protocol and UCP Ask: PAP’s UCP extension (read 2026-11-14) says Ask is in UCP’s current draft and ships in a later UCP release; the UCP repository backported dev.ucp.common.ask into release/2026-08-25 (PR 1024, 2026-11-02), and ucp.dev serves it as latest stable, although the v2026-08-25 tag does not include it. The orbit page takes no side and says only that the shopping, Ask included, runs over UCP; the UCP page carries the release status.

Errata

Corrections to the seed facts the research started from (the initial and follow-up research briefs), and where the corrected statement now lives.

Corrections to the seed facts in the initial research brief, from the follow-up research brief Section 2 and docs/factcheck-of-the initial research brief. Because the site content did not exist when the follow-up arrived (see AUDIT.md), every item below was applied at authoring time: the research and writer briefs carried the corrected wording. Columns: what the initial brief said, what is correct, source, files that carry the corrected statement (filled in during verification).

#Initial brief saidCorrectSourceFiles
2.1.1MPP IETF draft renamed 2026-09-09draft-ryan-httpauth-payment-01 expired 2026-09-18; draft-httpauth-payment-00 published 2026-06-19; -01 on 2026-09-09IETF datatrackerstripe-mpp timeline, facts
2.1.2Mastercard AP4M “cites MPP compatibility”Tempo lists AP4M as MPP-compatible; Mastercard does not. Superseded by R27 and R39: the site writes it as Tempo’s statement in Mastercard’s 2026-06-10 releaseTempo pages (or removed)mastercard-agent-pay, stripe-mpp relations, compare
2.1.3Web Bot Auth WG draft is “the basis” of TAPTAP (2025-10-14) uses RFC 9421 and is aligned with the Web Bot Auth direction but does not conform to the 2026-09-01 WG draftVisa spec, IETF draft, Cloudflare blogvisa-tap, orbit/web-bot-auth
2.1.4Scenario 8 combines Monetization Gateway with cloudflare:402 batch settlementMonetization Gateway beta settles USDC on Base through the Coinbase facilitator; cloudflare:402 is a separate credit-backed scheme variantCloudflare blog 2026-09-30, x402 specscenarios/crawler-pays-per-page
2.1.5L402 is “macaroon plus invoice”, “the ancestor of x402”bLIP-0026 is token-agnostic, macaroons optional; original Lightning Labs spec used macaroon plus BOLT11 invoice; no source states x402 lineagebLIP-0026, lightninglabs/L402x402, orbit/l402
2.1.6PayWord and MicroMint 1996LNCS volume dated 1997 (workshop 1996)DOI 10.1007/3-540-62494-5_6publications, timeline prehistory
2.1.7ERC-8004 testnets November 2025October to November 2025erc-8004 repoerc-8004 timeline
2.1.8“about 25 more mainnets”about 25 mainnets by August 2026 including Ethereum; dated table from READMEerc-8004-contracts READMEerc-8004 ecosystem
2.1.9AP2 production use unverified “outside UCP”unverified anywhere, including inside UCPAP2 and UCP reposap2, ucp, compare adoption
2.1.10AP2 v0.2 leaves step-up to networksv0.2 specifies no step-up; failures fall back through unresolved_constraint; only liability left to networksAP2 v0.2 docsap2 security
2.1.11FIDO formed two working groups on 2026-04-28only the Agentic Authentication TWG was new; the Payments TWG already existedFIDO announcementap2, mastercard-agent-pay, orbit/fido
2.1.12Visa MPP card spec 2026-03-18 “TAP headers optional”March spec uses VIC tokens and TAP; “optional” is from draft-card-charge-00 dated 2026-10-05. Superseded in part by R15: the sentence is in the draft from its first commit (2026-01-05), and the draft carries no date. Superseded by F40: added in PR 169, merged 2026-03-14, public 2026-03-18.mpp-specsstripe-mpp, visa-tap
2.1.13PyPI x402 legacyonly npm x402 and x402-express are V1; PyPI x402 2.x is V2. Superseded by R6: six npm packages are V1 legacyPyPI, repox402 ecosystem
2.1.14“Microsoft says it supports UCP”“MMC will support UCP” (future); Copilot Checkout requires a UCP-compliant feed (current)Microsoft announcementucp ecosystem
2.1.15x402scan operator unverified in one noteMerit Systems (Apache-2.0 repository)Merit-Systems/x402scanx402; research/conflicts.md
2.1.16STE rule 2.2 “then simplify”“then make it clear”research/ste.mdSTE guide
2.213 unsupported itemsverified, tagged reported, or removed per itemsee follow-upper item
2.37 internal inconsistenciesfixed per item (proofOfPayment off-chain; a2a-x402 targets AP2 v0.1; constraint key prefixes; closed Payment Mandate fields from schema; orbit links; MPP mention agreement)see follow-upper item

Found during research (session 2), beyond the follow-up

#Earlier text saidCorrectSourceFiles
R1Scenario 3 (follow-up wording): “a Google Pay handler that returns a network token”Google’s UCP FAQ says UCP checkout on Google surfaces uses only PAN_ONLY for Google Pay allowed_auth_methods; a network-token path through that handler is not documented for Google surfacesdevelopers.google.com/merchant/ucp/faqscenarios/shopper-in-gemini, ucp
R2UCP capabilities versioned independently since 2026-08-25core dev.ucp.* capabilities carry the release date; only third-party extensions version independentlyUCP v2026-08-25 schemasucp
R3UCP ES256 “mandatory”verifiers must support ES256; ES384 and EdDSA optionalUCP specucp
R4“No paper names UCP”; “no UCP conference talk”arXiv 2606.05043 models UCP checkout and 2602.06345 names UCP in its abstract; UCP sessions at the W3C and GS1 workshop on 2026-09-08arXiv; workshop pageucp section G and F
R5UCP “converging with ACP”no source supports convergence; only “no bridge” is supporteducp dossierucp, openai-acp
R6Follow-up 2.1.13: only npm x402 and x402-express are V1 legacysix npm legacy packages are V1 (x402, x402-axios, x402-express, x402-fetch, x402-hono, x402-next); PyPI x402 2.x is V2x402 repo typescript/packages/legacy/x402
R7Follow-up Appendix B: PayAI 1,000 free settlements per monththe cited secondary source says 1,000 free in total; unverified on PayAI’s pageWavect 2026-07-12x402 costs
R8“No AP2 podcast found”The Agent Factory Podcast episode on agent payments (Google Cloud Tech, 2025-09) linked from the AP2 READMEAP2 READMEap2 resources
R9Follow-up 2.1.8: Billions “has no dated entry”the contracts README added Billions on 2026-04-08; 25 mainnets including Ethereum are listed (24 others); dates are README listing dates, not deployment dateserc-8004-contracts README historyerc-8004 ecosystem
R10Testnet Validation addresses removed 2026-01-08removed from the README on 2026-01-06erc-8004-contracts commitserc-8004 timeline
R11Upgrade key holder “[verify]”on Ethereum and Base all three proxies are owned by one externally owned account (no contract code, so not a multisig); the holder is not publishedeth_call on public RPC, 2026-10-11erc-8004 security, compare
R12No published giveFeedback gas; registration “$1 to $5” on mainnetmeasured with eth_estimateGas on 2026-10-11: about 155k to 179k gas for a first feedback, about 203k for register; at the gas price observed that day this is cents on mainnet; method labeled, figures datedread-only RPC estimateerc-8004 costs
R13ERC-8126 Final “[verify, unusually fast]”Final confirmed on 2026-06-02 (Last Call 2026-05-12) while it requires ERC-8004, still DraftERCs repoerc-8004, orbit
R14T-REX 4.1.6 year unverifiedpublished 2024-10-18GitHub releaseorbit/erc-3643
R15Follow-up 2.1.12: “TAP headers optional” comes from draft-card-charge-00 dated 2026-10-05the sentence has been in the draft since its first commit on 2026-01-05; 2026-10-05 was only the snapshot date and the draft carries no date. Visa’s 2026-03-18 post says the card spec and mpp-card 0.1.8 are built on VIC and TAP. Superseded on 2026-10-19 (F40): the draft was added in PR 169, merged 2026-03-14, and published 2026-03-18; 2026-01-05 is an artifact of the squashmpp-specs history; Visa newsroomvisa-tap, stripe-mpp
R16TAP key directory mcp.visa.com/.well-known/jwks “[verify contents]”; examples use Ed25519the directory holds one 2048-bit RSA key whose certificate names vic-oauth-jwe.visa.com (Visa Sandbox Issuing CA); no Ed25519 key, so the spec’s example keyid cannot be resolved therefetched 2026-10-11visa-tap observability, security
R17TAP spec examplesthe example keyid, nonce, timestamps and signature reuse Web Bot Auth draft test vector E.2.2; browsing and checkout examples show the same signature, and the example window is 3,600 seconds against TAP’s own 8-minute limitTAP spec, IETF draftvisa-tap section B, H
R18“No paper names TAP”RAILS (arXiv 2606.08790) names TAParXivvisa-tap section G
R19visa/mcp repositorynow resolves to visa/ai (MIT, created 2025-11-05)GitHub APIvisa-tap resources
R20ACP authentication_required added 2026-01-30first appears in the 2025-12-12 schemaacp repoopenai-acp
R21ACP CLA signatories include “nekuda”the signatory is OpenCommerce Network Inc. (a nekuda GitHub user is listed); Agentic Commerce Inc. (Catalog) also signedacp repo CLA filesopenai-acp
R22ACP request signing “mandatory for Delegate Payment”mandatory only in RFC section 2.2; the same RFC’s header list says RECOMMENDED and the OpenAPI marks Signature optionalacp RFC and OpenAPIopenai-acp
R23ACP extensions: discount, affiliate attribution, marketing consentonly discount uses the extensions framework; affiliate attribution and marketing consent are fields defined by their own RFCsacp repoopenai-acp
R24ACP versions as releases; npm @agentic-commerce-protocol/specification [verify]0 GitHub releases and 0 tags; versions are dated spec folders (latest 2026-04-17); the npm package is not published (404); PyPI acp-sdk is IBM’s Agent Communication ProtocolGitHub API, npm, PyPIopenai-acp
R25ACP spec drift items[{id, quantity}]confirmed and wider: schema requires line_items, Item has no quantity, one example uses product_id; released snapshots were edited after release (2026-04-17 edited 2026-05-01)acp repo historyopenai-acp
R26Follow-up 2.1.1 draft datesconfirmed from the Datatracker: draft-ryan-httpauth-payment-00 2026-02-16, -01 2026-03-18, expired 2026-09-18 (record shows 2026-09-19 02:45 UTC); draft-httpauth-payment-00 2026-06-19, -01 2026-09-09, expires 2027-03-13; both individual submissions, no recorded “replaces” linkIETF Datatracker APIstripe-mpp
R27Follow-up 2.1.2: “Tempo lists AP4M as MPP-compatible”no Tempo or Mastercard page found that says so; claim dropped (unverified); only Tempo and Stripe being in AP4M’s initial partner group is supported (secondary)searched 2026-10-11stripe-mpp, mastercard-agent-pay
R28MPP design partners Anthropic, DoorDash, Mastercard, OpenAI and othersthose are named as Tempo partners for stablecoin work; only Visa is named an MPP design partnerTempo launch poststripe-mpp
R29Tempo “about 500 ms finality”blocks about every 600 ms (500 ms build loop plus network delay) with deterministic Simplex BFT finalityTempo docsstripe-mpp
R30MPP seed dates (subscriptions 2026-05-12, x402 support 2026-06-08, session v2 2026-06-17, identity 2026-08-12, CVEs 2026-03-31)blog or SDK dates; spec or code dates: subscriptions spec merged 2026-07-29; mppx 0.6.29 shipped x402 on 2026-06-02; session v2 spec merged 2026-06-25; identity code merged 2026-08-04 (npm 0.8.17 on 2026-08-10); advisories and fix 0.4.11 on 2026-03-26 (NVD 2026-03-31)mpp-specs, mppx, GitHub advisoriesstripe-mpp timeline
R31MPP session as an intentno generic session intent is standardized: PR #280 closed unmerged 2026-09-28; only charge and subscription are in specs/intents/; session is defined by the Tempo methodmpp-specsstripe-mpp
R32Session v2 “cuts costs by up to 72%”best case for one operation; settling to a new payee balance costs 79.4% more gasmpp-specs session v2stripe-mpp
R33MPPScan “about 4M transactions, $435K (2026-06-24)”those are the all-time values read on 2026-10-11 (4,072,426 transactions, $435,476); the June article shows live valuesmppscan APIstripe-mpp ecosystem
R34Rivest lottery tickets DOI10.1007/3-540-63594-7_87 (a nearby DOI resolves to a different paper)doi.orgpublications
R35Amazon v. Perplexity: injunction vacated, reported 2026-08-05Ninth Circuit opinion (No. 26-1444) dated 2026-08-04, read from the court PDF: vacated and remanded; the district court’s 2026-03-09 order date rests on press reports only (reported)Ninth Circuit opinion PDForbit, timeline Policy lane
R36Follow-up 2.1.5: “the current specification (bLIP-0026) is token-agnostic”bLIP-0026 is still an open, unmerged PR (#26) whose header says Active; its 2026-02-25 rewrite is token-agnostic (macaroons RECOMMENDED); the Lightning Labs repo adopted that text on 2026-03-10 and returned to macaroon= on 2026-03-20; LSAT first commit 2020-02-06, renamed L402 on 2023-04-20lightning/blips PR #26; lightninglabs/L402 commitsorbit/l402, x402
R37Cloudflare Radar “needs a free token”Radar API needs an API token; data licensed CC BY-NC 4.0 (Cloudflare docs)Cloudflare Radar docsorbit/cloudflare, methodology
R38Cloudflare NET Dollarannounced 2025-09-25; no evidence of launch foundCloudflareorbit
R39R27 (AP4M and MPP claim dropped)refined: Mastercard’s 2026-06-10 AP4M release quotes Tempo as “working with Mastercard on Machine Payments Protocol compatibility”; Mastercard makes no MPP claim in its own words; no Tempo page lists AP4M. Write it as Tempo’s statement, sourced to that releaseMastercard newsroom 2026-06-10mastercard-agent-pay, stripe-mpp, compare
R40Verifiable Intent constraint keys mandate.payment.amount_range, types with .1those strings exist only on VI main (2026-04-20, PR #23, a breaking rename without a version bump); at tag v0.1.0 the names were payment.amount, payment.allowed_payee and types without .1verifiable-intent repomastercard-agent-pay, ap2
R41DTVC as “an agentic token formatted for card fields”DTVC is a one-time security code issued with a Mastercard Virtual Card Token; Mastercard expands it both as “Validation Code” and “Verification Code”Mastercard developer docsmastercard-agent-pay, glossary
R42Mastercard agent identity “as a browse or pay tag”Mastercard’s developer guide gives one tag, Agent-pay-auth (glossary writes agent-pay-auth); agent-browser-auth and agent-payer-auth are Visa’sMastercard developer guidemastercard-agent-pay, visa-tap compare
R43Mastercard key directory “[verify URL]”unknown: the only host in the docs, agentpay-key-directory.mastercard.com, does not resolve; Cloudflare’s post names noneDNS check 2026-10-11mastercard-agent-pay observability
R44Acceptance Framework 2025-10-14; Trust Framework white paper 2026-09-30Mastercard says only “October 2025”; no Trust Framework white paper found (the 2026-09-30 release names the framework, the US probability score test and Skyfire as KYA partner)Mastercard newsroommastercard-agent-pay timeline, publications grey list
R45VI v0.1.0 dated 2026-02-19CHANGELOG date 2026-02-19; the git tag sits on a 2026-03-05 commitverifiable-intentmastercard-agent-pay timeline
R46R7 / Appendix B PayAI feePayAI’s own docs: 1,000 free credits per receiving wallet for life, not per month; since 2026-09-21 each settlement costs gas plus 30 percent, paid in $0.001 credits; the facilitator home page still shows the older plan (both recorded)PayAI docsx402 costs
R47Stripe SPT “private preview, no pricing”Stripe docs now say “Public preview”; no pricing published (pricing half superseded by F55: the pricing page lists 0.15 USD per SPT issued)Stripe docsopenai-acp, stripe-mpp
R48Keyrock “$73M in the year to May 2026”window May 2025 to April 2026, covering 176M on-chain transactionsForkLog report of Keyrockmarket
R49McKinsey 2025-10-17; Morgan Stanley 2025-12-08McKinsey report dated October 2025 (day unconfirmed); Morgan Stanley earliest report 2025-12-09publisher pages, pressmarket
R50Prehistory: EMVCo tokenisation framework 2014; LSAT around 2020EMVCo v1.0 2014-03-11 (trade press, reported); LSAT launch post 2020-03-30; renamed L402 2023-04-20 (repository commit); HTTP 402 reserved in RFC 2068 (1997-01), RFC 2616 (1999-06), RFC 9110 (2022-06); RFC 9421 and 9530 February 2024rfc-editor.org, Lightning Labs, Crossreftimeline Prehistory lane
R51“GENIUS Act says nothing about AI agents”it does not cover agents as payers, but Section 9 mentions artificial intelligence as an AML detection method for Treasury to studyGENIUS Act textcompliance rows
R52“Card-network live agent transactions are controlled pilots”no source says this directly; closest is Mastercard’s “first agentic transaction” remark on its Q3 2025 call (reported); write “named transactions are pilots or first transactions” with sourcesearnings call coveragevisa-tap, mastercard-agent-pay, market
R53x402 dossier: TypeScript facilitator client timeout 30 secondsDEFAULT_TIMEOUT_MS = 90_000 in httpFacilitatorClient.ts (90 seconds); the flow file and playground use 90x402 SDK sourcex402 flows, playground
R54Follow-up 2.2: say “built on Mastercard tokenization” unless a Mastercard page names MDES; the site said no Mastercard page names MDESMastercard developer pages (release history, Virtual Card Token tests) do name MDES for Token Connect and Virtual Card Tokens; the agentic-token pages do not. Wording: agentic tokens are “built on Mastercard tokenization”; MDES is named only where Mastercard names itdeveloper.mastercard.com release history and mvct testsmastercard-agent-pay (claims 007, facts, FAQ, flashcard, resources)
R55Mastercard: “the network adds an agent flag to the authorization message”Stripe says only that additional information is included in the authorization message; no data element is namedStripe docsmastercard-agent-pay body, open questions
R56Verifiable Intent L1 “about 1 year”, L2 Immediate “about 15 minutes” as limitsthe spec states these lifetimes as recommendations, not hard limitsverifiable-intent specmastercard-agent-pay

Found during the 2026-10-18 fact check

Every claim and statement on the ERC-8004 page, and the cross-site statements about it, was checked against its sources on 2026-10-18 (report: verification/erc-8004-2026-10-18.md). These rows record what the site said and what is correct.

#The site saidCorrectSourceFiles
F1Twenty ERC-8004 mainnets were listed in the contracts README at once on 2026-03-06 (refines R9)Fifteen were listed in eight commits on the default branch, four of them pull requests, from 2026-02-02 (Polygon) to 2026-02-12; five more (GOAT Network, Metis, SKALE Base, Soneium, XLayer) followed on 2026-03-06, for 21. GitHub’s path-filtered history hides the February commitsfirst-parent history of master; PRs 33, 37, 39, 40erc-8004 page, claims 100, 103, 188, timeline, ecosystem chart, source record for the README history
F2The playgrounds run on a “fake” chain id 424242424242 is assigned to Fastex Chain testnet; the playgrounds now use 402402, which the public chain registry did not assign on 2026-10-18chainid.networkerc-8004, x402 and stripe-mpp playgrounds and tests, page notes, docs
F3The ERC-8004 registries have no payable functionNo function takes or forwards payments; the only payable entry point is the owner-only upgradeToAndCall inherited from OpenZeppelin UUPScontract ABIserc-8004 claim 017, FAQ, facts, ecosystem
F4All giveFeedback fields except value and valueDecimals are optionalagentId must be a registered agent; tag1, tag2, endpoint, feedbackURI and feedbackHash are optionalERC-8004 texterc-8004 claim 054, flashcards
F5“Stripe’s MPP discovery draft”The payment discovery draft’s authors are from Tempo Labs and Merit Systemsdraft-payment-discovery-01 author blockerc-8004 page, claim 162
F6ERC-3643 has no agent concept; its transfers check the sender’s identity; ERC-8004 has no delegation modelERC-3643 defines an Agent role (an operator that automated systems may fill) and checks the receiver’s identity plus the compliance rules; ERC-8004 operators can manage an agent, but nothing scopes what it may spendERC-3643 texterc-8004 page, claim 180, orbit/erc-3643
F7ERC-8122 is an extension that builds on ERC-8004ERC-8122 is an alternative ERC-6909 registry; ERC-8217 and ERC-8126 require ERC-8004ERC-8122, ERC-8217, ERC-8126 textserc-8004 page, claims 135, 136
F8No ERC3643 Association or Tokeny statement about AI agents was foundA Tokeny post of May 2023 discusses AI agents and tokenization; no statement about ERC-8004 or agent identity standards was foundtokeny.comerc-8004 page, claim 182
F9No source was found for an October 2025 “finalized” announcementA press release of 2025-10-13 called it “the finalized version”; ERC-8004 was never Final and returned to Draft on 2026-01-13press release, ERC historyerc-8004 claim 186
F10The testnet listings ran to 2025-11-03To 2025-11-05, when PR 6 mergedcontracts repositoryerc-8004 page, claim 098
F11The registries are “live on 25 mainnets”; at least 23 run version 2.0.0 and Billions could not be reachedListed on 25; 24 return 2.0.0, Billions included; Soneium still runs the 1.0.0 placeholderread-only RPC calls, 2026-10-18erc-8004 page, claim 221, ecosystem, compare cells
F12Explorers count more networks, which suggests community deploymentsAt least five chains the README does not list (Arc, Shape, Tempo, LUKSO, Gate Layer) run the same 2.0.0 registries under the same owner accountread-only RPC calls, 2026-10-18erc-8004 page, claim 226, ecosystem
F13The Graph launched the Agent0 subgraphs on 2026-04-14The Graph announced on 2026-04-14 that the subgraphs were live and already queried millions of times; no launch date is givenThe Graph blogerc-8004 claim 121, facts, timeline, ecosystem
F14Publication notes: Jiang et al. 2026 models protocols “around ERC-8004”; Acharya foreshadows what AP2 and ERC-8004 “later formalize”; Chan et al. is a “direct ancestor”; Vaziry and Ventirozos are directly about ERC-8004None of these papers names ERC-8004 in a way that supports the note; Acharya came after both; no source states the lineage; tags and notes correctedthe paperspublications, erc-8004 publication tags and resources
F15The agent0-sdk snippet assigns the result of registerIPFS() to a registration fileregisterIPFS() returns a transaction handle; the file comes from waitConfirmed()agent0-sdk 1.7.1 type definitionserc-8004 code
F16Methodology: links and publications are checked on every buildThey are checked by hand with pnpm verify:links and pnpm verify:citations; the build runs neitherpackage scriptsmethodology page
F17Playground: an operator could still bind a wallet after the agent was transferredA transfer clears the token approval, and operator approvals belong to the old owner, so the call reverts “Not authorized”; the playground now does the sameIdentityRegistryUpgradeable.sol, OpenZeppelin ERC721erc-8004 playground
F18No agent-specific Visa rule or liability allocation was publicVisa’s rules govern Visa and its member institutions, confer no rights on third parties and yield to applicable law (1.1.1.5, 1.1.1.3). Since 2025-10-18 they have required an Agentic Payment Provider to enroll in Visa Intelligent Commerce and register with Visa, directly or via an Agentic Payment Enabler (4.1.24.2). Within Visa’s system they make the cardholder responsible for its actions in an Agentic Transaction as if the cardholder had initiated it (4.1.24.10), and treat it as the Cardholder for such a transaction (glossary). Visa calls none of its agent rules a liability shift and adds no agent-specific dispute condition, fee or interchange rate, but issuers must pay for Agentic Transactions made under the cardholder’s payment instructions and must not block them wholesale (1.7.6.1, 1.7.4.1), and from 2026-10-24 a provider’s login ID counts among the evidence that can defeat a card-absent fraud dispute (Dispute Condition 10.4). Worldpay (2026-07-30) says no liability shift exists yet. Legal limits and the risk allocation added 2026-10-19Visa Core Rules and Visa Product and Service Rules, 2026-04-18 edition; Worldpay 2026-07-30; Mastercard Rules, 2026-06-02 editioncompliance tables of erc-8004, x402, visa-tap, openai-acp, ucp and ap2 (with the Agentic Payment Provider definition on openai-acp and ucp, and a Mastercard row on five of them), and the compliance summaries of visa-tap, ap2 and mastercard-agent-pay; visa-tap claims 171 and 238, page, FAQ, open questions, personas and costs; ap2 open questions and issuer persona; orbit/visa-intelligent-commerce; scenario agent-shops-with-visa-card; personas ai-platform and network; glossary; research/policy
F19GENIUS Act final rules were still pendingNo primary federal regulator had issued a final rule by 2026-10-18, but Treasury’s procedural interim final rule took effect on 2026-09-30Federal Register 2026-19966erc-8004 compliance, research/policy
F20Compliance rows assigned duties broadly (OFAC screening by “whoever sends the payment”, GENIUS Act “applies to payments”, California rules on “automated scoring of people”, MiCA covering “wallet providers”, and five more)Rewritten from the primary legal texts, naming the parties each text namesOFAC FAQ 560, Public Law 119-27, CPPA regulations, MiCA, AI Act, TFR, UK MLRs, PIPEDA, MAS guidelineserc-8004 compliance
F21File hashes live in the off-chain feedback filesfeedbackHash and responseHash are logged on-chain in events; proofOfPayment stays in the off-chain fileERC-8004 texterc-8004 controls, compare cells
F22One owner key can upgrade every registryOn Ethereum and Base one externally owned account owns all three proxies; on BSC a 3-of-5 Safe owns Identity and Reputation and an EIP-7702 account owns Validationread-only RPC calls, 2026-10-18erc-8004 controls, security, compliance, compare cells
F23Agent ids are “free to mint”There is no protocol fee; a registration costs gas (about 203,000)contract code, gas measurementerc-8004 page, facts, FAQ
F24A first giveFeedback costs about 155,185 to 178,504 gasThat range holds for an agent that already has clients; for one with none it is about 172,409 to 193,006gas measurement, 2026-10-11erc-8004 claim 143, scenario agent-buys-one-api-call, compare cells
F25ERC-8226 is the bridge that uses ERC-8004 as the identity layer and ERC-3643 as the compliance layerERC-8226 is agnostic to the identity system and the token standard; it names ERC-8004 and ERC-3643 or ERC-7943 as examplesERC-8226 texterc-8004 facts, glossary, open questions, resources, relations, timeline, orbit/erc-3643
F26The Stablecoin Act in Bill C-15 received Royal Assent on 2026-03-26 and applies to issuers (read as in force)It received Royal Assent on 2026-03-26 but is not in force: Justice Laws (current to 2026-09-30) marks every provision not in force, and section 97 leaves commencement to orders of the Governor in CouncilJustice Laws, Stablecoin Act (S-15.9)erc-8004 compliance, research/policy
F27The x402.org “Last 30 days” counter was last updated on 2026-08-25The counter carries no date and has shown the same values (75.41M transactions, $24.24M) in every archived copy from 2025-12-14 to 2026-10-12 and live on 2026-10-19; 2026-08-25 is only the page-edit date in its markdown renditionWayback Machine capturesx402 page, FAQ, open questions, observability, compare cell, metrics, timeline, resources, claims 194 to 196
F28x402 section B opening: the server never touches a chain; the facilitator lets the server respond, then settles; x402 makes no statement about the clientA server may settle directly; the default flow is verify, resource, settle, then respond; the payment itself does not identify the client, but optional extensions canx402 README, spec v2 section 6.1, extension specsx402 page, STE, facts (the CLAUDE.md copy of this exemplar is left to the owner)
F29x402 has no separate docs license and asks for GPG-signed commits, not a DCO sign-offThe technical charter puts documentation under CC BY 4.0 (9.b.iv) and requires a DCO sign-off on inbound code (9.b.ii); the repository LICENSE is Apache-2.0 and CONTRIBUTING.md requires signed commitsx402 technical charter, 2026-03-31x402 page, claims 027 and 028, compare cells
F30x402 SECURITY.md routes reports to Coinbase’s HackerOneSince 2026-10-15 (PR 3823) reports go privately to a TSC member or primary maintainer; a bug bounty is “coming soon”x402 repositoryx402 open questions, claim 136
F31Stripe’s x402 support was for US businesses onlyAll US states except New York, plus more than 30 countries on requestStripe docs, 2026-10-19x402 compliance, timeline, claim 171
F32A signed x402 payment cannot be recalled before it expires; time windows bound every authorizationx402 has no recall message, but an unused EVM authorization can be canceled on chain before settlement (EIP-3009 cancelAuthorization, Permit2 nonce invalidation, ERC-7710 revocation); batch-settlement vouchers carry no expiryEIP-3009, Base USDC bytecode, x402 scheme specsx402 controls, compare cells, personas
F33The TypeScript SDK covers network families “to Lightning”; Express answers 502 when a facilitator is unreachableNo SDK implements the Lightning binding; 502 means a timeout or malformed answer, and a refused connection gives 500 or 402x402 SDK sourcesx402 page, flows, state machine, playground, claim 247
F34The arXiv 2607.19545 finding that all 15 facilitators broke a rule is not in the abstractThe abstract states itarXiv 2607.19545x402 security, claim 140
F35Smaller x402 corrections: first exact spec commit 2025-02-23 (it is 2025-02-22), GHSA-qr2g dated 2026-03-07 (2026-03-06), Bazaar returns “listings, not categories” (listings carry tags and 30-day counts), Circle publishes no fee schedule (it says no per-transaction fees), Agentic Wallets “announced” (live since 2026-02-11), double charging (double service), refunds “only” in auth-capture (Solana upto also returns escrow), the Python snippet (raised TypeError), invalid EIP-55 placeholdersCorrected from the cited sourcesas in verification/x402-2026-10-19.mdx402 files
F36x402 cross-site statements: the seller carries the settle-timeout risk; nothing marks a payment as x402; amounts stay private; anyone with a wallet can pay the Monetization Gateway; upto is a Permit2 ceiling everywhere; Kite’s x402 support is only on social media; RFC 9421 appears only in cloudflare:402; L402 alignment on 2026-03-10The client carries the risk; facilitator addresses or builder codes mark payments; amounts are public on chain; the beta is for eligible US buyers; Solana upto uses an escrow channel; Kite’s docs describe it; RFC 9421 is also in an extension and the lnbtc rules; 2026-03-11as in verification/x402-2026-10-19.mdscenarios, flows, orbit pages, personas
F37The TAP specification names https://mcp.visa.com/.well-known/jwks as Visa’s key storeThe specification named that URL until at least 2026-10-10 and names none after Visa moved its documentation in October 2026; Visa’s own token manager uses that key set to encrypt tokens for its MCP server, so it is not a confirmed TAP agent-key store, and how production agent keys reach verifiers is not publicTAP specification (current and 2026-10-10 Wayback copy); github.com/visa/ai token managervisa-tap claims 069, 074, 112, 239, page, FAQ, quiz, flashcards, diagrams, flows, state machine, scenario, observability, compare cell, glossary
F38Visa calls none of its rules (or no rule) a liability shiftVisa calls none of its agent rules a liability shift; Dispute Conditions 10.1 and 10.2 are titled “EMV Liability Shift”. This refines F18Visa rules, 2026-04-18 editioncompliance rows of six protocols, Mastercard summary, visa-tap page, FAQ, orbit page, personas, research/policy
F39Unattributed statements that no liability shift exists (issuer, merchant-enterprise and psp personas; dispute and refund cells)Attributed to Worldpay (2026-07-30) with its hedge (fraud scope; non-fraud disputes unsettled), with Visa’s issuer payment duty and the 2026-10-24 login-ID dispute evidenceVisa rules; Worldpaypersonas, visa-tap controls and compare cells
F40The MPP card draft’s TAP sentence dates from its first commit on 2026-01-05 (R15)Added in mpp-specs PR 169, merged 2026-03-14 while the repository was private, published in the init commit on 2026-03-18github.com/tempoxyz/mpp-specs/pull/169visa-tap claims 187 and 212, page, source notes
F41VIC provisions a token after step-up and passkey, and the purchase instruction is created before the passkey step; VIC REST calls go to sandbox.mcp.visa.comThe token is provisioned first, then step-up and passkey where required; the passkey result travels inside POST /vacp/v1/instructions; REST calls go to sandbox.api.visa.comVIC documentation; github.com/visa/aivisa-tap claims 140, 141, 245, VIC flows, scenario
F42Smaller Visa TAP corrections: dynamicData sits inside the Token object (it is a sibling); Akamai verifies Mastercard Agent Pay (TAP only); the sample sends an X-Payment header (ad hoc X-Payment-* headers); the overview “still says” development and deployment (retired in October 2026); RAILS is the only paper naming TAP (several do); the know-your-agent announcement was 2026-09-11 and builds on TAP (2026-09-10, builds on MAS’s SAFR); Cloudflare is a steward (a development partner); 4,700 percent in the year to August 2025 (July 2025, year over year)Corrected from the cited sourcesas in verification/visa-tap-2026-10-19.mdvisa-tap files, orbit pages, publications
F43OpenAI has not published a fee rate for ChatGPT checkoutOpenAI’s merchant page (read 2026-10-20) says there are no fees for purchases completed on the merchant’s own site or app, and its FAQ says there are no fees on purchases that start in ChatGPT and that OpenAI is moving away from a standalone Instant Checkout experience, with purchases completed on merchant-owned sites or apps (exact end date unpublished). The 2025 “small fee” statement and the reported 4 percent for Shopify merchants are dated history; Shopify’s Agentic Storefronts Supplemental Terms (2026-10-06, section 6.1) confirm a per-channel fee set in Shopify Admin with no printed ratechatgpt.com/merchantsopenai-acp claim 193, page, FAQ, costs block
F44OpenAI’s Apps SDK docs; Stripe lists UCP or ACP for selling through agents; an SPT is deactivated when consumed, expired or revoked; Visa and Mastercard tokens under SPTsOpenAI renamed the documentation to Plugins (external checkout approval limited to physical goods; a saved-payment-methods checkout path added); Stripe restructured its docs and gives ACP and UCP separate protocol pages; granted SPTs can also be resolved once into credentials by a PCI-attested seller (a “resolved” deactivation reason); American Express tokens are named beside Visa and MastercardOpenAI plugin docs; Stripe agentic commerce and SPT docs, 2026-10-20openai-acp claims 125, 164, 166, 183 to 189, 203, 211, 215, page, resources, ecosystem, relations, scenario, orbit/openai-apps-sdk
F45ACP does not name GDPR; California’s automated-decision rules apply from 2026-01-01ACP’s marketing consent RFC cites GDPR, CAN-SPAM and CCPA; the California rules took effect 2026-01-01 with compliance due by 2027-01-01 for significant decisions. Also: the CFPB absence row now names its search and date; the AI Act row carries the Article 50(2) date for generative systems already on the market (2026-12-02); the UK SCA clause cites the Payment Services Regulations 2017, regulation 100; the Canada row dates only the risk-management and safeguarding requirements (2025-09-08); the PSD3 row is datedACP rfc.marketing_consent.md; CPPA regulations section 7200(b)openai-acp compliance
F46The ChatGPT scenario’s delegated-payment payload; handler_id optional and instrument required; the checkout state machine’s cancel edges and the in_progress to completed edge; agent and merchant “authenticate each other with bearer tokens”The payload lacked the required display_card_funding_type; handler_id and instrument are required together (or purchase_order_number alone for B2B); cancel is allowed from any non-final status (405 only when completed or canceled); the in_progress to completed transition is inferred from status values; the merchant authenticates the agent with a bearer token while the agent verifies webhooks with an HMAC secretACP 2026-04-17 JSON Schemas and checkout RFCopenai-acp flows, field table, state machine, playground, page
F47STE: create a session with the line items and the currency; the ACP specification does not define six checkout status valuesCreating a session also needs the agent’s capabilities; the RFC text does not describe six of the eleven status values that the JSON Schema listsACP 2026-04-17 JSON Schemaopenai-acp STE
F48Smaller ACP corrections: the repository has been quiet since 2026-07-18 (now dated: no maintainer comment, review, merge or commit between 2026-07-18 and 2026-10-20; the one maintainer action was closing SEP PR 178 unmerged on 2026-08-09); a partner quotation attributed to OpenAI; “Stripe engineer” (developer advocate); the playground listed as planned; undated absence claims; the 2025-11-21 timeline event (the agreement is dated that day; Stripe and OpenAI signed the CLA); Walmart listed as announced although its ChatGPT app was live on the web from 2026-03-24; “SPT allowances” with a signing algorithm in global personas (ACP allowances or SPT usage limits); the reason given for scaling back Instant Checkout (OpenAI cited a lack of flexibility)Corrected from the cited sourcesas in verification/openai-acp-2026-10-20.mdopenai-acp files, personas
F49Google and the UCP project publish no merchant counts; Universal Cart is announced; Shopify’s default activation of Google checkout has no primary sourceGoogle said on 2026-09-16 that UCP enables direct checkout for “hundreds of thousands of brands and retailers” (no exact count or volume); Universal Cart launched in the US on 2026-10-15 with checkout through UCP; Shopify’s help pages say direct checkout is on by default for eligible US stores with no fees beyond payment processing; Microsoft says it takes no commission today; Target is live per its fact sheet of 2026-06-18, Shopify merchants per Shopify’s help, and Walmart is named only in Google’s 2026-10-15 postGoogle posts of 2026-09-16 and 2026-10-15; Shopify Help Center; Microsoft’s pageucp claims 184, 186, 190, 191, page, FAQ, facts, ecosystem, timeline, compare cells
F50Critics point to Google’s structural control of UCPThe governance facts hold (a permanent council seat, the proxy for open seats until December 2028, custody of ucp.dev), but no published critique of them was found; stated as the atlas’s own observationUCP GOVERNANCE.md; searched press 2026-10-20ucp claim 209, page
F51Example payloads and the webhook exampleFour flow payloads fail the v2026-08-25 schemas (missing line-item totals, schema URLs, the ucp envelope, payment_handlers); the webhook example omitted the UCP-Agent header and signed too few components (content-type is required when a body is present; the 2026-10-16 draft adds webhook-id and webhook-timestamp)UCP schemas and signatures text at cd78fb3; PR 659ucp flows, Gemini scenario flow, page
F52AP2 production use is unverified “outside UCP” (compliance persona)Unverified anywhere, including inside UCP (follow-up 2.1.9); also Microsoft’s UCP support stated in the present tense on the Shopify orbit page (Microsoft says Merchant Center will support UCP)the follow-up research brief 2.1.9; Microsoft’s pagepersonas/compliance, orbit/shopify-agentic-storefronts
F53Every UCP entry carries a required version plus optional spec, schema, id and config; every response carries ucp.status; fulfillment also extends cart; UCP never defines a wallet of its ownPayment handler entries require id, platform profiles require spec and schema, business capabilities require schema, business REST, MCP and A2A services require endpoint; ucp.status defaults to success; fulfillment extends checkout and catalog, discount and buyer_consent extend checkout and cart; UCP does not currently define a handler, card network or walletUCP schemas and docs at cd78fb3ucp claims 060, 061, 235, page, field tables
F54Smaller UCP corrections: the lodging capability “merged on 2026-09-25” (merged 2026-09-24, announced 2026-09-25); the 2026-03-19 update “reported only” (Google’s own post exists); the Warren letter cited to press (the senator’s release is primary); YouTube attached to Direct Offers (Shopping ads on YouTube); the pub-jiang-2026-formal paper tagged UCP (it never names UCP); Google’s retention “until the user requests deletion” (the FAQ says indefinitely until the user explicitly requests deletion; the site had omitted the word); the California automated-decision compliance date; undated absence claims; the AI Act row lacked the 2026-12-02 Article 50(2) transition; the Singapore PDPA row was labeled reported with “statute site blocked” (the statute site answers); the Canada rollout timing (Australia and Canada follow next year per Merchant Center help)Corrected from the cited sourcesas in verification/ucp-2026-10-20.mducp files, publications, compliance
F55Stripe Shared Payment Tokens had “no published price” (MPP and ACP pages, Mastercard cost row; follow-up Appendix B and 3.3; supersedes the pricing half of R47)Stripe’s US pricing page lists 0.15 USD per SPT issued, in every archived copy from 2026-04-23 on; the page names no paying partystripe.com/pricing (Wayback 20260423031430 to 20261020161141)stripe-mpp, openai-acp, mastercard-agent-pay claims, sidecars, personas
F56Stripe’s 1.5 percent stablecoin fee was “reported” by the press onlyStripe’s own pricing page lists stablecoin payments at 1.5 percent of the amount (conversion, screening and gas sponsorship included); whether it applies to MPP charges is still not statedstripe.com/pricingstripe-mpp claims 165 and 166, Costs, compare cell, open question
F57Four or five mppx advisories, one Rust advisory, “six SDK advisories”, “the worst incidents were SDK bugs, not protocol flaws”Nine published repository advisories (mppx 5, Rust mpp 2, pympp 2), all fixed, none reported exploited; a 2026-08-30 formal analysis reports 12 new MPP cases not shown exploitable; minimum versions Rust mpp 0.12.0 and pympp 0.10.1, latest mppx recommendedGitHub repository advisories (2026-10-21), arXiv 2609.00060stripe-mpp security, controls, personas, compare cells
F58Live figures and versions of 2026-10-11 (mppx 0.13.4, “under one cent” per MPPscan transaction, 126 of 129 listings, Tempo Wallet MPP Credits live, Lightspark “announced”)mppx 0.14.1 (2026-10-21), pympp 0.14.0, Rust mpp 0.16.0, mpp-rb 0.1.9; MPPscan 30-day average about 1.1 cents; 135 of 138 listings accept Tempo; MACH replaced MPP Credits for new purchases; Lightspark’s lightning SDK is live on npmnpm, PyPI, crates.io, RubyGems, MPPscan API, mpp.dev, wallet.tempo.xyzstripe-mpp page, claims, ecosystem, compare cells, open questions
F59Mastercard Agent Pay listed as composing with MPP; relation typed compatible-with; “Stripe runs MPP”The only link is Tempo’s statement; Mastercard’s 2026-10-20 Early Access brief builds AP4M on x402 and names no MPP; Stripe co-authors MPP with TempoMastercard newsroom 2026-06-10 and 2026-10-20stripe-mpp page, relations, compare cells; openai-acp and mastercard-agent-pay relation notes and compare cell
F60Flow and diagram errors: invalid EIP-55 placeholder addresses, topUp sent to the escrow, card, SPT and MCP flows dated with the core draft’s 2026-09-09, JWE “RSA-OAEP”, HMAC slot order attributed to the posted -01Lowercase placeholders as the Tempo specs require; topUp goes to the server, which broadcasts; each flow carries its own draft’s date; RSA-OAEP-256 with A256GCM; the slot order is the repository text after PR 362research/vendor/mpp-specs at 50309c8, posted draft textstripe-mpp flows, diagrams, playground, page
F61Legal rows: “only proposed GENIUS Act rules”, Regulation Z for every card charge, the Transfer of Funds Regulation scope and what MPP credentials carry, the MAS stablecoin framework’s scope, “card economics are unchanged”Treasury’s interim final rule took effect 2026-09-30 and no primary-regulator final rule exists; Regulation Z for credit cards only; travel rule scope per Regulation (EU) 2023/1113 and the ledger addresses credentials carry; MAS framework only for SGD or G10 pegged stablecoins issued in Singapore; SPT price notedFederal Register, eCFR, EUR-Lex, MASstripe-mpp compliance.json
F62Smaller MPP corrections: three new headers (not two), “Visa network tokens”, Stripe added cards on 2026-04-29, the session intent as a third standardized intent, publication tags on papers that never analyze MPP, MPP glossary meanings on unrelated pages, wrong “latest tag” in GitHub snapshotsAccept-Payment, Payment-Authorization and Payment-Receipt; card network tokens from a Visa-written method; cards through SPTs since the 2026-03-18 launch; session is defined per method; four tags removed; glossary terms scoped by page; snapshots prefer the latest releasecore draft, Stripe launch post, papers, codestripe-mpp page, timeline, glossary, publications; rehype-glossary, GitHub fetcher
F63FIDO “gave no deliverable or date” stated as current; FIDO drafts “member-only”FIDO’s Payments Technical Working Group presented targets on 2026-09-08 (public repository for review in September 2026, harmonized AP2 and Verifiable Intent by end 2026, first consolidated version mid-2027); no public draft found as of 2026-10-21; FIDO publishes working drafts openly in general, so “member-only” had no sourceFIDO slides at the W3C and GS1 workshop; FIDO specification and working-group pagesap2 claims 020, 021, 206, 209; page, open questions, compare cells; orbit fido-passkeys-agentic
F64AP2 mechanics stated too broadly: every mandate and receipt bound to the checkout hash; iat and exp on every mandate; expiry the only end of an open mandate; “liability stays with the networks”; a deterministic signer duty; “a security layer, not a payment protocol”Only closed mandates carry the checkout hash and receipts hash the closed mandate; iat and exp are optional (exp recommended for open mandates); budget and recurrence limits also end an open mandate; AP2 assigns no liability and offers evidence; the Shopping Agent must not present overlapping mandates; AP2 is not a commerce protocol or a payment railresearch/vendor/AP2 at e1ea56d (specification, schemas, security considerations)ap2 page, STE, controls, glossary, flashcards, security, compare cells
F65ERC-8226 “uses ERC-8004 as its identity layer”ERC-8226 is agnostic to the agent identity system and names ERC-8004 as one exampleeips.ethereum.org EIP-8226clm-ap2-157, ap2 page, ap2-composition diagram
F66Publications: arXiv 2607.21824 tagged to OpenAI ACP and UCP with unnamed platforms; AP2 described with v0.1 intent and cart mandates in several notes; AP2 called a rail; tags on papers that never name AP2The paper reports 14 vulnerabilities in AP2 v0.2.0 and names neither UCP nor OpenAI’s ACP; notes use v0.2 terms; AP2 is an authorization layer; two tags removed; new records for arXiv 2610.21063 (five of its attacks apply to AP2: three rejected, two partial) and the 2025-10-27 PayPal announcementarXiv 2607.21824, 2610.21063; Google Cloud post 2025-10-27publications, ap2 and openai-acp and ucp security and tags, ap2 timeline and ecosystem
F67Legal rows: Visa summary overreach, PSD2 “consent to the specific transaction”, AI Act Article 50 dates, PIPEDA scope, MAS EUPG covering Singapore-issued cards, Regulation P for any Credential Provider, OFAC duties on a few parties only, undated PSD3, RPAA and CFPB absencesCanonical Visa wording; consent may be given in advance and for a series (PSD2 Art 64); 2026-12-02 for Article 50(2) on generative systems already on the market; PIPEDA and EUPG scope as on the Visa TAP page; Regulation P only for covered institutions; OFAC binds all U.S. persons; absences dated with their searchDirective 2015/2366, Regulation (EU) 2026/1744, OFAC FAQ 560, 12 CFR 1016, MAS EUPGap2 compliance; MAS EUPG rows on openai-acp and ucp
F68Smaller AP2 corrections: “developed with more than 60 organizations”, the Know Your Agent announcement dated 2026-09-11 and “building on” TAP, the open mandate always user-signed, field-table schema links, receipt timestamps before their mandate, a misplaced error branch, “AP2 is Google’s open protocol” on the Mastercard page, persona step-up wordingGoogle collaborates with more than 60 organizations and named 16; the announcement is dated 2026-09-10 and explores common principles through BuildFin.ai; the agent provider signs in the Trusted Agent Provider model; links and flows corrected; AP2 was launched by Google and contributed to FIDOGoogle launch post; The Asian Banker 2026-09-10; AP2 specificationap2 claims, page, flows; mastercard-agent-pay page and claim 006; personas issuer and consumer
F69Agent Pay for Machines “launched” with no availability; “no Agent Pay technical document mentions x402”; MPP listed as composing with Agent PayAnnounced 2026-06-10; Early Access opened 2026-10-20 (first buyer- and seller-side APIs, toolkit, sandbox, documentation) after pilots with Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and Hype; Mastercard says AP4M builds on x402; no pricing, no general availability date, no MPPMastercard news brief 2026-10-20mastercard-agent-pay page, claims, timeline, ecosystem, compare cells, relations; x402 page, relations, timeline, composition diagram
F70Mastercard pages “never name MDES” for agentic tokens (follow-up 2.2 wording)Mastercard’s Agent Pay developer page (read 2026-10-21) names network tokenization via MDES; since 2026-08-05 the MDES Customer Service API offers token spend controls for Agent Pay issuersdeveloper.mastercard.com Agent Pay use case; MDES Customer Service release notes July 2026claims 007 and 244, page, facts, faq, flashcards, glossary
F71No Agent Pay Trust Framework white paper was foundMastercard published “Trust for agentic commerce” (September 2026, 16 pages) with the 2026-09-30 release: five capabilities, an Agent Pay Ready mark, named offerings including Agentic Disputes; no specification, volumes, pricing or liability rulemastercard.com white paper and landing pageclaims 071 and 249 to 252, page, publications
F72“No agent-specific reason codes or liability shift were published”, sourced to a review that covers only a price tableNo public agent-specific reason code or liability rule; the 2026-06-02 Rules require Agent Pay participants (9.2.4, 9.5.1) to follow Mastercard Agent Pay Program Standards, which are not public; standard chargeback rights applyMastercard Rules 2026-06-02claim 207, page, facts, faq, controls, compliance, compare cells, personas, glossary, scenario
F73“No public revocation path” for tokens; “no public SDK or sandbox”Mastercard documents MVCT token deletion and issuer suspend or cancel notifications (no public API revokes an agent or Agentic Token); AP4M Early Access offers APIs, a toolkit and a sandbox, and a login-gated Agent Pay developer service existsdeveloper.mastercard.com MVCT pages; 2026-10-20 briefcontrols, compare cells, claim 109, faq, personas, scenario
F74Edge verification drawn in a different order without the 8-minute window cap; Level 3 example payload with wrong field names; a Web Bot Auth test-vector key id presented as invented; the key directory “hosted” by MastercardMastercard’s nine-step Level 1 checklist with the 8-minute cap; orderTotalAmount.amount, itemUnitPrice and itemDeliveryMethod; placeholders; Cloudflare’s future tense, and the example host does not resolveMastercard Level 1 and Level 3 guides; Web Bot Auth draft; DNSdiagrams, STE, playground, flows, claims 085, 086, 189
F75Smaller Mastercard corrections: Acceptance Framework date unknown, probability score “in testing”, issuer enablement “in several regions”, 97 Verifiable Intent stars, publication tags on papers that never name Mastercard, “no paper analyzes Agent Pay”, legal rows (CCPA ADMT, AI Act, MAS EUPG, Regulation E, PSD2, PIPEDA, RPAA)Introduced 2025-10-14; rolling out for US testing (announced 2026-09-30); Europe confirmed, US and Latin America announced; 101 stars; five tags removed and RAILS added; no security analysis found; settled legal wordingMastercard story 2025-10-14, release 2026-09-30, GitHub, arXiv, legal textsclaims, page, ecosystem, publications, compliance

Found during the 2026-11-14 refresh

The 2026-11-14 refresh re-checked every protocol for changes since its last fact check, applied every update for OpenAI ACP and the big updates elsewhere, and had each writer’s changes checked by an independent critic (reports: verification/<slug>-2026-11-14.md and verification/refresh-2026-11-14.md). These rows record statements the site published before the refresh that were wrong, or that later became wrong while the site still presented them as current. Dated statements that later events overtook are described in the reports, not here.

#The site saidCorrectSourceFiles
F76OpenAI’s documentation uses /product_feeds paths, webhook names order_created and order_updated, 201 on completion, 409 for an idempotency conflict and TLS 1.2 or later (present tense; the same differences in the FAQ, two flows, the quiz, a flashcard, a persona and the docs-versus-spec diagram)These differences describe OpenAI’s ACP docs as read 2026-10-11 and 2026-10-20. OpenAI replaced those docs in its 2026-11-12 to 2026-11-13 docs rewrite with the Commerce in ChatGPT partner playbook, and none of the five values appears in its current commerce or plugin docs (2026-11-14). The ACP side (/feeds, order_create and order_update, 200, 422, TLS 1.3) is unchanged, and the comparison is now labeled a dated snapshotOpenAI Commerce in ChatGPT partner playbook and its full docs export (2026-11-14); Internet Archive captures of OpenAI’s ACP docs (2026-08-10 to 2026-11-07); ACP specification 2026-04-17openai-acp page (Limitations, status codes note, comparison table), FAQ, quiz, flashcards, personas, two flows, docs-vs-spec diagram; claims 132, 157, 219, 220
F77OpenAI reserves direct Delegate Payment integration for PSPs and PCI DSS Level 1 merchants with their own vaults, may require a PCI attestation of compliance before production access, and says the feed and checkout specs carry no cardholder data (present tense)OpenAI’s Checkout API reference for ChatGPT plugins lets a PCI DSS Level 1 merchant receive raw card data by implementing the ACP Delegate Payment endpoint (2026-11-14). The PSP reservation, the attestation and the cardholder-data statements are dated to OpenAI’s ACP docs as read 2026-10-11, which the 2026-11-13 docs rewrite replaced, and the rewritten commerce docs do not mention PCIOpenAI Checkout API reference for ChatGPT plugins (2026-11-14); OpenAI Commerce in ChatGPT partner playbook (2026-11-14)openai-acp claims 048, 151, 152, page (Actors and roles), PCI compliance row, threat t6; ChatGPT scenario
F78ChatGPT feed onboarding is limited to approved partners who apply through a formSince the 2026-11-13 docs rewrite, OpenAI’s developer docs send businesses to Business Hub (Businesses in ChatGPT, introduced 2026-11-10) to claim a profile and verify their identity before uploading products; OpenAI’s merchant page still shows an application form and a waitlist (2026-11-14)OpenAI Submit product feeds guide (2026-11-14); OpenAI News RSS item Introducing Businesses in ChatGPT (2026-11-10); OpenAI merchant page (2026-11-14)openai-acp claim 117, compare cells, controls, personas; ChatGPT scenario and flow
F79OpenAI’s own feed API uses /product_feeds paths and adds a promotions API, OpenAI recommends a full daily file plus API updates during the day, and the ACP Feed API carries the product feed into ChatGPTOpenAI’s rewritten commerce docs document no feed API: businesses deliver full snapshots in OpenAI’s flat feed format by manual upload, a hosted URL or SFTP, with no stated cadence (2026-11-14). The /product_feeds paths, the promotions API and the daily-file advice are dated to the docs as read 2026-10-11. OpenAI’s Ads Delta Feeds API updates feed products with an ACP-shaped PATCH /feeds/{feed_id}/products, and OpenAI’s merchant page still says shopping is built on ACPOpenAI Submit product feeds guide, product feed schema and Ads Delta Feeds API reference (2026-11-14); OpenAI merchant page (2026-11-14)openai-acp claims 115, 116, observability, product feed flow; ChatGPT scenario, flow and context diagram
F80OpenAI asks merchants to allowlist its published egress IP ranges for ACP calls (an edge control)OpenAI publishes egress IP ranges for ChatGPT integrations and says an allowlist does not replace request authentication; its cloud browser needs no allowlist, and sites should verify its Web Bot Auth signatures before granting an exception (2026-11-14). The allowlist request is dated to OpenAI’s ACP docs before the 2026-11-13 rewriteOpenAI IP egress ranges page and cloud browser access guide (2026-11-14)openai-acp claim 141, page (security summary), threat t1, edge control; ChatGPT scenario
F81OpenAI excludes products such as adult content, alcohol, nicotine, gambling, weapons and prescription-only medicines from ChatGPT shoppingOpenAI’s plugin guidelines list prohibited goods for plugins, such as adult content, gambling, tobacco and nicotine, weapons and prescription and age-restricted medications, and do not name alcohol (2026-11-14). The alcohol exclusion is dated to OpenAI’s ACP docs as read 2026-10-11OpenAI plugin guidelines (2026-11-14)openai-acp claim 154, US compliance row; ChatGPT scenario and flow
F82OpenAI’s developer docs still describe the three flows Instant Checkout needs (product feed, checkout, payments); a resource note says the Eco explainer covers the Instant Checkout retirementOpenAI’s rewritten commerce docs (2026-11-13) no longer describe Instant Checkout, and its plugin guidelines still list it as a beta for select marketplace partners (2026-11-14). OpenAI scaled Instant Checkout back in 2026 and published no end date, so the note now covers the 2026 scale-backOpenAI plugin guidelines (2026-11-14); OpenAI Commerce in ChatGPT partner playbook (2026-11-14)openai-acp claim 225, page (What changed), resources (Eco note), dossier
F83Smaller ACP corrections: OpenAI calls Stripe’s SPT the first Delegate Payment compatible implementation; the reference implementations are OpenAI’s and Stripe’s hosted services, and the ACP README points merchants to OpenAI’s implementation; OpenAI’s merchant page cannot be dated earlier than 2026-10-20 because Wayback copies are JavaScript shells; a reported 4% OpenAI fee for Shopify merchants among the ChatGPT scenario’s costs; American Express ACE with status Announced and its own agent registration; Amazon v. Perplexity as a court case over scrapingThe ACP website calls Stripe, with its SPT, the first compatible PSP, and OpenAI’s docs called the SPT the first compatible implementation only until the 2026-11-13 rewrite; the README still names both, but its OpenAI link now opens the Commerce in ChatGPT partner playbook, which does not describe ACP; a readable 2026-04-04 Internet Archive capture already has the page’s current sentences; the 4% was a 2026-01-21 report about Instant Checkout, and Shopify says selling in ChatGPT carries no fees beyond standard payment processing (2026-11-14); OpenAI’s 2026-11-13 Wallet post quotes American Express calling Wallet its first ACE integration (reported, with no American Express statement as of 2026-11-14), and the agent registration is planned, with its specification still under development; the case is about agent accessAgentic Commerce Protocol website (2026-11-14); OpenAI Commerce in ChatGPT partner playbook (2026-11-14); Internet Archive capture of OpenAI’s merchant page (2026-04-04); Shopify Help Center, Selling on ChatGPT (2026-11-14); OpenAI, Introducing ChatGPT Wallet (2026-11-13); American Express agentic commerce page (2026-11-14); CourtListener dockets of Amazon v. Perplexity (2026-11-14)openai-acp claim 049, page (framing paragraph, actors and roles), FAQ, flashcard f4, compare cell, ecosystem, merchant-page record; ChatGPT scenario; orbit pages openai-apps-sdk and amex-ace; persona ai-platform; stripe-acs orbit page and its openai-acp relation note
F84Both published x402 advisories so far concern SDK packages, and neither has a CVE identifierThe two advisories the maintainers published still have no CVE, but since 2026-10-20 CVE-2026-113603 (medium), assigned by the third-party CNA VulnCheck, covers a sign-in-with-x payment bypass in the SDKs; GitHub mirrors it as the unreviewed GHSA-vxw2-vmfp-vrg3 with no package mapping, and its fix (PR #3840) was still open on 2026-11-14CVE-2026-113603 record (VulnCheck, 2026-10-20); GitHub Advisory Database; x402 issue #3838 and PR #3840x402 claims 134 and 266 to 269, page, security, compare cell, open questions, observability, facts, timeline
F85To close route-matching bypasses, upgrade @x402/core, and until then declare HEAD routes explicitly or reject HEAD on paid paths; the legacy V1 package x402 1.2.0 listed with no security caveatThat advice covers V2 only. The deprecated V1 middleware (npm x402 1.2.0, used by x402-express and x402-hono) has an open parameterized-route bypass (issue #3850, public since 2026-10-19), and on 2026-11-14 no V1 release fixed it or carried the HEAD or paywall script-injection fixes, although the READMEs promise security patches; V1 servers need to migrate to the @x402 packages (2.29.0 or later), since a HEAD workaround alone does not close the V1 gapsx402 issues #3850 and #4038; npm registry (2026-11-14); x402 legacy package READMEsx402 security (route-matching threat), ecosystem (legacy SDK note), page, claims 272 and 273, facts, FAQ, compare cell
F86The x402.org home page shows a Last 30 Days counter (75.41M transactions, $24.24M volume) that has not changed since at least 2025-12-14The counter never changed and is gone: captures show the same values from 2025-12-14 to 2026-10-24, the page was last edited on 2026-10-27, and on 2026-11-14 it showed no counter, only an FAQ line about millions of transactions; the removal was not announced. The site keeps it as dated history beside x402scan (about 4.93M transactions and $1.89M for the 30 days to 2026-11-14) and agenteconomy.to (about 200.2M transactions and $43.0M cumulative as of 2026-11-14)x402.org and its sitemap (2026-11-14); Wayback Machine capture of 2026-10-24; x402scan; agenteconomy.tox402 claims 194, 196 and 256, page, FAQ, resources, observability, compare cell, metrics, open questions, source record
F87Batch-settlement vouchers stay in server storage until the server claims them on chainThey stay off chain until claimed, with the server by default; since 2026-10-26 the EVM batch-settlement specification (v1.1) also defines a facilitator-managed mode in which the facilitator keeps them, shipped in Go v2.29.0 (2026-10-28) and @x402/evm 2.30.0 (2026-11-04)x402 EVM batch-settlement specification v1.1 (PR #3725, merged 2026-10-26); Go v2.29.0 and @x402/evm 2.30.0 changelogsx402 claim 165, observability
F88Coinbase Agentic Wallets are live, and Coinbase’s docs describe a managed agent wallet that holds USDC and pays for x402 services through the awal CLI or an MCP server (available since 2026-02-11)By 2026-11-14 the Agentic Wallet docs answered 404 and the CDP changelog no longer carried the 2026-02-11 entry; no retirement was announced and the npm packages are not deprecated, so the status is unknown. CDP’s Agentic Accounts overview now lists Wallet MCP (x402 exact, upto and auth-capture on Base and Base Sepolia) and Coinbase for AgentsCoinbase Developer Platform docs and changelog (2026-11-14); npm registry (awal, @coinbase/payments-mcp)x402 claims 180 and 278, ecosystem, page, orbit/coinbase-agent-products
F89Smaller x402 corrections: latest SDKs @x402/core 2.28.0 (2026-09-29) and PyPI x402 2.25.0 with 36 releases; the Go module requiring Go 1.24; SDK parity with TypeScript covering 13 network families, Go evm and svm, and Python evm, svm and tvm@x402/core 2.31.0, PyPI x402 2.28.0 (39 releases) and Go v2.31.0 since 2026-11-12, with Go 1.26.10 required since v2.29.0 (2026-10-28); the TypeScript table lists 14 network families, 13 of them on npm, Go adds casper and Python adds cardano and client hooks (2026-11-14)npm registry, PyPI and the Go module proxy (2026-11-14); x402 SDK features table on the main branchx402 page key facts and versioning, claims 037, 041 to 043 and 175, compare cells, ecosystem SDK list, FAQ, open questions
F90A contract answers at the scripted Validation address, but it is not listed or announced as deployedThe ERC-8004 maintainers have not listed or announced it, but Circle’s Arc documentation lists that address as Arc Mainnet’s ValidationRegistry, already in a capture of 2026-10-12 (read 2026-11-14); ‘not officially deployed’ holds only in the sense of a deployment by the maintainersCircle’s Arc documentation, contract addresses page (2026-10-12 capture, read 2026-11-14); ERC-8004 contracts READMEerc-8004 claims 083 and 086, page, FAQ, observability, controls, ecosystem, personas, STE, validator persona
F91Hundreds of thousands of registrations (adoption radar)Millions: 8004scan counted 2,062,896 agents on 2026-11-14 (reported), about three times its 2026-10-18 count, almost all of the growth from Central City batch registrations on Base (2026-10-20 to 2026-10-23) and Arc Mainnet (2026-11-01 to 2026-11-06); 0G holds about 3.94 million more ids that 8004scan does not index, so registrations across the chains exceed 6 million8004scan statistics API (2026-11-14); read-only registry calls on Base, Arc and 0G (2026-11-14)erc-8004 compare cells (radar and adoption), page, claims 145, 146 and 227 and new claims 234 to 237, ecosystem metrics, facts, timeline
F92Smaller ERC-8004 corrections: Visa’s agentic platform rule cited as section 4.1.24.2Section 4.1.23.2 in the 2026-10-24 edition of Visa’s rules (4.1.24.2 before; the substance is unchanged)Visa Core Rules and Visa Product and Service Rules, 2026-10-24 editionerc-8004 compliance
F93The Web Bot Auth working group draft finds keys through the Signature-Agent URL, by default a directory at /.well-known/http-message-signatures-directory (or a JWK Set URI or client metadata document), and serves its key directory as application/http-message-signatures-directory+jsonSince draft -01 (2026-10-29) a verifier fetches each Signature-Agent URL directly as a JWK Set; the well-known URL is one such URL, the directory, jwks_uri and cimd types are gone, and the directory media type is required only at the well-known URI. TAP still looks keys up by keyid in the payment scheme’s key storeIETF Web Bot Auth working group draft -01, draft-ietf-webbotauth-httpsig-protocol-01 (2026-10-29)visa-tap claims 112 and 218, page (Compare and compose), TAP versus Web Bot Auth diagram, playground comparison
F94Mppx.create answers an invalid request attestation with HTTP 401 and an absent attestation or unresolved key with HTTP 403; the MPP documentation says a request attestation does not authorize a payment or prove the end user’s identityBoth described mppx’s request attestation, which mppx 0.16.0 (2026-10-28) replaced with per-route identity: TAP moved to mppx/extensions/identity/tap, and passing attestation to Mppx.create now throws. Since 0.18.0 (2026-11-09) a route that requires TAP answers a missing or invalid signature with 401 and an untrusted or unresolvable key with 403. The identity page that replaced the docs read on 2026-10-07 no longer carries that sentence (read 2026-11-14); the site now describes TAP in mppx as an identity check that runs before any payment Challenge and still pairs with an MPP payment credentialwevm/mppx CHANGELOG and npm releases 0.16.0 to 0.19.0 (2026-10-28 to 2026-11-14); MPP documentation, Identity page at mpp.dev/extensions/identity (2026-11-14)visa-tap claims 214 and 215, page (Compare and compose)
F95Visa’s VIC developer docs have required sign-in since October 2026, and Visa’s agent onboarding process is not publicOn 2026-11-14 the VIC docs were public again without sign-in. They outline the production path: onboarding to VIC, TAP, Visa Token Service and Visa Payment Passkeys, plus registration in the Visa Agent Registry Service (VARS) so that Visa can validate agent signatures and merchant encryption keys. The VARS reference is still restricted, so the registration steps are not public, and the docs state no fees, so the fee text rests only on the 2026-10-03 archiveVisa Intelligent Commerce developer docs: overview, concepts and production readiness pages (2026-11-14); Visa TAP API reference navigation, Visa Agent Registry Services bundle restricted (2026-11-14)visa-tap page (Actors), compare cells, controls, security summary, costs caveat, resources, context diagram; Visa Intelligent Commerce orbit page (TAP inside VIC, Status); VIC source notes
F96Visa’s agent rules sit in section 4.1.24 of the current rules edition (2026-04-18), and Visa adds no agent-specific 3-D Secure ruleThe current edition is dated 2026-10-24: it renumbers the agent section to 4.1.23 with the same rule IDs, and its summary of changes lists no agentic change. The rules still add no 3-D Secure rule, but Visa’s VIC product docs (2026-11-14) give US merchants that support 3-D Secure a “Program Not Supported” response for agentic transactionsVisa Core Rules and Visa Product and Service Rules (2026-10-24 edition); Visa Intelligent Commerce developer docs (2026-11-14)Visa Intelligent Commerce orbit page (rules paragraph)
F97Smaller Visa TAP corrections: the Visa card scenario flow said the POST /vacp/v1/cards request body is not shown because it is not public; the page’s versioning paragraph said twelve later pull requests to the sample repository are open or were closed unmergedVisa’s public VIC API reference documents that request body (bundle VACP.100, read 2026-11-14), so the flow now says only that it omits it; thirteen as of 2026-11-14 (nine open, four closed unmerged), with still nothing merged since 2025-10-28Visa API reference, Visa Intelligent Commerce POST /vacp/v1/cards (2026-11-14); GitHub visa/trusted-agent-protocol (2026-11-14)agent-shops-with-visa-card scenario flow (step 2), visa-tap page (Versioning)
F98UCP checkout runs in the US today, and Google says Australia and Canada follow next yearGoogle began rolling out UCP direct checkout to Canadian shoppers on AI Mode in Google Search and the Gemini app on 2026-11-04, naming lululemon, select Shopify merchants, Shoppers Drug Mart and Simons, with retailers as seller of record. The next-year date in Google’s Merchant Center help (read 2026-11-14) covers only self-serve onboarding for Australia and Canada. Universal Cart stays US-only, and no Google launch post names Australia or the UK (as of 2026-11-14)Google Canada blog post (2026-11-04); Google Merchant Center Help, onboarding to the UCP integration hub (read 2026-11-14)ucp compliance summary and Canada row, page status and key facts, compare cells (maturity, adoption), ecosystem, Gemini scenario; claims 242 and 257
F99dev.ucp.common.ask is a draft on main only, in no releaseAfter Shopping Tech Council approval on 2026-10-30, PR 1024 backported Ask into the release/2026-08-25 branch on 2026-11-02. ucp.dev serves it as part of 2026-08-25 (read-only questions over REST POST /ask or the MCP tool ask_business), but the v2026-08-25 git tag does not contain it. Shopify said on 2026-11-06 that Ask is live across its storefronts under the 2026-08-25 profile (Shopify’s statement; the allbirds.com profile is one example)UCP pull request 1024; UCP Shopping Tech Council minutes (2026-10-30 and 2026-11-06); ucp.dev 2026-08-25 Ask documentation (read 2026-11-14)ucp claims 047 and 253 to 255, page (status, versioning, field table), namespace diagram, compare cells, ecosystem
F100Google’s UCP requests carry a UCP-Agent header and a User-Agent beginning with Google/UCPGoogle’s UCP FAQ (last updated 2026-11-03) lists the User-Agents Google-Shopping-Merchant-Integration, Google/UCP* and Google-UCP-Prober/1.0, and its network guide (last updated 2026-10-30) names Google-Shopping-Merchant-Integration the default outbound client and says Google/UCP* is sent when origin user-agent propagation is enabled. Profile discovery and token requests carry no UCP-Agent, and Google says neither header alone should authenticate a request. The FAQ the site read on 2026-10-20 (updated 2026-10-16) said the User-Agent begins with Google/UCP; that wording was gone by 2026-10-30Google UCP Guide, Frequently Asked Questions (last updated 2026-11-03) and Network and WAF configuration (last updated 2026-10-30)ucp claim 157, page (actors and roles), observability, Gemini scenario step 3 and its flow
F101Microsoft says it takes no commission on Copilot Checkout todayMicrosoft’s Copilot Checkout page said so when the site read it on 2026-10-20. The answer was removed by about 2026-11-06 (archive captures show it on 2026-11-04 and the smaller page from 2026-11-06), and the page as read on 2026-11-14 makes no fee statement either way. A removed answer is not evidence of a fee; Shopify’s Copilot channel page says its merchants pay only standard payment processing feesMicrosoft Advertising, Agentic commerce and Copilot Checkout page (read 2026-10-20 and 2026-11-14; archive captures for dating only); Shopify Help Center, Selling on Microsoft Copilot (read 2026-11-14)ucp claim 240, page (compare and compose), FAQ, compare cells (fees, who pays), ecosystem cost row
F102Shopify’s direct checkout in Google AI Mode and Gemini is on by default for eligible US stores (based in the US, selling to US customers)Shopify’s help center (read 2026-11-14) says eligible stores may be based in any country and must sell to customers in the US, Canada or Australia, with the checkout rolling out gradually to customers in those three countries; the page changed between 2026-10-19 and 2026-11-03 (archive captures, dating only). Australia rests on Shopify’s statement, since Google has announced Canada only (2026-11-04)Shopify Help Center, Selling on Google AI Mode and Gemini (read 2026-11-14); Google Canada blog post (2026-11-04)ucp claim 184, page (limitations), ecosystem Shopify rows, facts, open questions, Shopify orbit page
F103Shopify Agentic Storefronts reach ChatGPT, Microsoft Copilot, Google AI Mode and Gemini, with checkout active by default for eligible US stores (Shopify orbit page)Shopify’s Help Center (read 2026-11-14) lists four AI channels: ChatGPT, a discovery-focused referrer whose buyers check out on the store’s own site, and three with a Shopify-powered direct checkout on by default for eligible stores: Google AI Mode and Gemini, Microsoft Copilot and Meta (an AI channel since 2026-09-08; Meta surfaces including Muse when available). Eligibility differs by channel (Google: customers in the US, Canada or Australia; Copilot: US customers; Meta: 11 countries), and no channel adds fees beyond payment processing. The two Help Center pages the orbit page cited now redirect to the main page, which it now cites with the four channel pagesShopify Help Center, Shopify agentic storefronts and the Selling on ChatGPT, Google AI Mode and Gemini, Microsoft Copilot and Meta pages (read 2026-11-14); Shopify changelog, Meta is now an AI channel in your admin (2026-09-08)orbit shopify-agentic-storefronts (status, body, sources); ucp claim 261
F104Smaller UCP corrections: Universal Cart keeps one cart across Search, Gemini, YouTube and Gmail; tag v2026-08-25 is commit cd78fb3, and the release branch differs from it by PR 871; two arXiv papers name UCP; no source supports UCP and ACP converging; the Microsoft orbit page cited Microsoft’s requirements page for its ACP statementSearch and the Gemini app, with YouTube and Gmail planned; cd78fb3 is the original cut, the tag was moved on 2026-10-22 or 2026-10-23 to 87dd4b1, which includes PR 871, other backports and rich media variants, and since 2026-11-02 the branch is one commit ahead with the Ask backport; at least three arXiv preprints name UCP, including 2610.17378 (2026-10-12); still no bridge or mapping, but OpenAI’s plugin guide (2026-11-13) shows a reference checkout that follows UCP’s field names and enums without naming either protocol; only the 2026-01-08 launch post says Microsoft is adopting ACP, and the requirements page names ACP in no version read from 2026-10-11 to 2026-11-14Google Universal Cart posts (2026-05-19 and 2026-10-15); UCP GitHub releases and tags (read 2026-11-14); arXiv 2610.17378 (2026-10-12); OpenAI Build a plugin guide (2026-11-13); Microsoft Advertising Copilot Checkout launch post (2026-01-08) and requirements pageorbit google-universal-cart; ucp claim 249 and page (field-table note, versioning); ucp FAQ, security summary, compare cell and publication tag; ucp page and open questions; orbit microsoft-copilot-checkout
F105In the core draft “a 403 means the payment was valid but policy denies access”, given as the draft’s only 403 case (message flow, status table, quiz q6, policy-denied flow, metered-inference scenario)Still true of draft-httpauth-payment-01 as posted to the IETF on 2026-09-09. The repository text of 2026-11-11 (mpp-specs PR #404, an in-place edit that paymentauth.org serves under the same name) adds a second case after a paid request, in which other authentication denied access and nothing settled; servers should say which case applies in the Problem Details body and must verify other authentication before verifying or settling a Payment credentialTempo Labs and Stripe, mpp-specs PR #404 and the core draft at commit 7bb99c8 (2026-11-11); draft-httpauth-payment-01 as served by paymentauth.org (dated 2026-11-11) and as posted in the IETF archive (2026-09-09)stripe-mpp claim 093 (new claims 262 to 266), page (message flow, status table), quiz q6, controls, policy-denied flow, metered-inference scenario
F106“mppx adds optional RFC 9421 request attestation for Web Bot Auth and Visa TAP” (page, claim 134, controls, compare cells, visa-tap relation, personas, resources)mppx 0.16.0 (2026-10-28) replaced request attestation with per-route identity, a breaking change: Mppx.create no longer takes an attestation option and the TAP and Web Bot Auth profiles moved under mppx/extensions/identity. By 0.19.0 (2026-11-14) built-in verifiers also cover Email OTP, Link agent identity, Persona, World ID and Tempo ID, all outside the specs and with identity headers that no draft defineswevm’s mppx CHANGELOG at the 0.19.0 release (2026-11-14); mpp.dev identity page and “Expanded identity primitives” post (2026-11-11)stripe-mpp claim 134 (new claims 272 to 275), page (Extensibility), controls, compare cells (identity model, layers covered), visa-tap relation note, personas, resources
F107“The latest mppx release is 0.14.1” (page header and key facts “mppx 0.14.1 (2026-10-21)”, claim 046)The latest is mppx 0.19.0 (2026-11-14), five minor releases on; 0.16.0, 0.17.0, 0.18.0 and 0.19.0 carry breaking changes, and since 0.18.0 the Tempo server methods throw at construction in production when no store is passed. Claim 046 now reads as of 2026-10-21npm registry entry for mppx and wevm’s mppx CHANGELOG (2026-11-14)stripe-mpp page header and key facts, claim 046 (new claims 267 to 271), What changed
F108“Rails add methods without approval” (governance field, claim 012, compare cells)Anyone can implement an MPP method without approval, as mpp.dev’s governance page says, but Tempo maintainers decide which methods enter the official mpp-specs repository: on 2026-10-25 one of them closed six external method pull requests as networks too small for the official specmpp.dev governance page (Tempo Labs and Stripe, unchanged on 2026-11-14); mpp-specs PR #377 and five other method pull requests closed on 2026-10-25 (GitHub)stripe-mpp governance field, claim 012, page (design goals, governance), compare cells (permissionless detail, openness radar)
F109Smaller Stripe MPP corrections: the solana method “charge, session” (methods table and methods map); the Tempo page’s latest version “node release v1.16.1”solana also specifies subscription since 2026-10-25 (draft-solana-subscription-00, by two Solana Foundation authors); Tempo’s latest node release is tempo/v1.18.3 (2026-11-12), after the T13 upgrade reached mainnet on 2026-11-03mpp-specs PR #310 (GitHub, 2026-10-25); Tempo node releases on GitHub and Tempo’s T13 upgrade pagestripe-mpp methods table and methods map; tempo orbit page
F110Delegate SD-JWT, the draft that chains AP2 mandates, is “an individual draft” posted to the IETF on 2026-04-22, “not adopted by a working group” (stated as current)The IETF OAuth working group adopted it on 2026-10-30 as draft-ietf-oauth-delegate-sd-jwt-00 (G. Oliver, Google; C. Bormann, SPRIND; intended status Standards Track), replacing the individual draft of 2026-04-22, which had expired on 2026-10-23; it is still an Internet-Draft, not an RFC. AP2 v0.2 cites the pre-adoption text, and its Python SDK still writes the intermediate typ kb+sd-jwt+kb that the working group draft renamed kb-sd-jwt+kb (as of 2026-11-14)IETF Datatracker record and text of draft-ietf-oauth-delegate-sd-jwt-00 (2026-10-30); Google’s AP2 repository at e1ea56d (Python SDK)ap2 page (buildsOn, Limitations), claim 108, resources, glossary
F111Agent Pay’s status is “pilot”, and “Named transactions so far are pilots or first transactions” (intro, status note, key facts, ELI5, deployments paragraph, facts, FAQ, compare cells); live agent transactions “are still controlled pilots” (network persona)Mixed as of 2026-11-14: regional pilots plus early live use through partners. Shopify said on 2026-10-28 that Shop Pay agent purchases from merchants off Shopify use Mastercard, Visa and Discover tokens (Agent Pay, per Mastercard’s CEO on 2026-10-29, reported); Travelport, Booked AI, Basis Theory and Mastercard announced a live flight purchase on 2026-11-12; ChatGPT Wallet, built with American Express, Mastercard and Visa, began rolling out on 2026-11-13 in dots for US ChatGPT Pro subscribers without naming a Mastercard program. Most transactions in Mastercard’s own releases are still pilots, and no volume is published (the CEO called the numbers not yet significant). The network persona’s Visa half now names the live B2B pilot that Visa, BILL and Billtrust announced on 2026-10-20. Radar values unchangedShopify, Fall ‘26 Edition (2026-10-28); The Motley Fool, transcript of Mastercard’s Q3 2026 earnings call (2026-10-29); Travelport press release with Booked AI, Basis Theory and Mastercard (2026-11-12); OpenAI, Introducing ChatGPT Wallet (2026-11-13); Visa release on the BILL and Billtrust pilot (2026-10-20)mastercard-agent-pay page (status, status note, intro, key facts, ELI5, deployments paragraph), facts, FAQ, compare cells (maturity, adoption evidence, radar justifications), network persona
F112Mastercard says VI is being embedded in the payment flow, “but no public document shows a VI chain checked in a live authorization” (Limitations, open question 1, issuer and network personas, radar justification); the scenario: “No public source shows it in a live purchase”, with every Verifiable Intent step marked live use not shown publiclyA joint release by Travelport, Booked AI, Basis Theory and Mastercard (2026-11-12) says Verifiable Intent linked the customer’s approval to one live Agent Pay flight purchase, so a payment that did not match would not have proceeded. It names no Verifiable Intent layer or mode and does not say who checked the chain, and no public record shows the Autonomous-mode layers in live use; the site words it as the companies’ statementTravelport press release with Booked AI, Basis Theory and Mastercard (2026-11-12); PYMNTS (2026-11-12)mastercard-agent-pay page (Limitations), open question 1, personas (issuer, network), radar justification; scenario mastercard-token-in-checkout-form with its flow and context diagram
F113Smaller Mastercard Agent Pay corrections: Asia-Pacific and EEMEA firsts “begin” on 2026-02-17 (timeline); the key directory sits at /.well-known/http-message-signatures-directory on the Signature-Agent host, as the Web Bot Auth drafts define it (observability)EEMEA began with the UAE pilot of 2025-11-19 (Majid Al Futtaim and Dataiera), which Mastercard called Agent Pay’s first transaction outside the US, and Australia’s controlled trials of 2026-01-28 already preceded the row, now titled Further Asia-Pacific and EEMEA firsts (2026-02-17 to 2026-07-08); since Web Bot Auth draft -01 (2026-10-29) the Signature-Agent value is itself the URL of a JWK Set and the well-known path is one special case, and the Agent Pay directory’s location is still unknown (example host NXDOMAIN on 2026-11-14)Mastercard EEMEA newsroom (2025-11-19); IETF draft-ietf-webbotauth-httpsig-protocol-01 (2026-10-29)mastercard-agent-pay timeline, observability
F114The Web Bot Auth working group draft is -00, and Signature-Agent points to the signer’s key directory, by default at the well-known path (glossary: the bot publishes its keys in a directory)Revision -01 (2026-10-29) is current: each Signature-Agent member is an HTTPS URL that the verifier fetches directly as a JWK Set, the well-known directory is only the special case for a whole domain, and the bare string form is legacy; deployed signers and verifiers, such as ChatGPT’s cloud browser and Cloudflare, still use that string form (2026-11-14)IETF Web Bot Auth working group, draft-ietf-webbotauth-httpsig-protocol-01 (2026-10-29); OpenAI, Help ensure cloud browser access to your site (Commerce in ChatGPT docs, 2026-11-14)orbit web-bot-auth (status, latest version, What it is), glossary web-bot-auth and signature-agent (plain and STE), publication pub-meunier-2026-webbotauth
F115MCP uses dated revisions and the atlas reads revision 2025-11-25; MPP’s MCP transport places capability advertisement and payment data in MCP’s _metaThe current revision is 2026-07-28, released on 2026-07-28, before the page was checked on 2026-10-11; it is stateless, with no initialize handshake or Mcp-Session-Id. MPP’s transport was written against 2025-11-25: payment support is advertised in the initialize handshake that 2026-07-28 removes, and only credentials and receipts travel in _meta (2026-11-14)Model Context Protocol, Versioning page and Key Changes for specification 2026-07-28; Tempo Labs, Payment Authentication Scheme JSON-RPC and MCP Transport (draft-payment-transport-mcp-00, mpp-specs)orbit mcp (status, MPP bullet)
F116World AgentKit is a beta, and the docs still label it betaWorld marked the agentkit repository deprecated, naming no replacement, and archived it on 2026-10-20; by 2026-11-14 the AgentKit docs overview answered 404 and its integration page redirected to World’s Agent Pass quickstartWorld, worldcoin/agentkit pull request 44 (2026-10-20) and repository; World Developer Docs (2026-11-14)orbit world-agentkit (status, oneLiner, body, x402 relation note)
F117A2A’s steward is the A2A Project at the Linux Foundation, and A2A is published as a Linux Foundation project (glossary: an open standard hosted at the Linux Foundation)Since 2026-08-17, before the page was checked on 2026-10-11, A2A has been a hosted project of the Agentic AI Foundation (AAIF), a Linux Foundation directed fund, after starting at Google (2025-04-09) and moving to the Linux Foundation (2025-06-23)Agentic AI Foundation, A2A joins AAIF’s open agentic stack (2026-08-17); A2A Project releases and governance on GitHuborbit a2a (steward, status, body), glossary a2a
F118Global timeline, Market lane: after Mastercard’s first agentic transaction (2025-10-30), card-network agent payments remained limited pilotsA year later Mastercard still published no agent volume, while its CEO described early consumer adoption, with Shop Pay using Agent Pay and Mastercard network tokens and an OpenAI partnership that includes Agent Pay (2026-10-29 call, reported)Mastercard Q3 2026 earnings call transcript (The Motley Fool, 2026-10-29)research/market.json Market-lane event 2025-10-30 (global timeline)
F119AP2 and Verifiable Intent produce signed mandates, but production use is unverified anywhere, including inside UCPProduction use is barely documented: no public deployment is shown to use AP2 mandates; in one live flight purchase, per Travelport, Booked AI, Basis Theory and Mastercard (2026-11-12), Verifiable Intent linked the customer’s approval to the payment; neither is shown inside UCP, and who verifies a mandate chain is not publicTravelport, Booked AI, Basis Theory and Mastercard, joint release on the live agentic flight purchase (2026-11-12)persona compliance (pains)
F120Glossary: OpenAI’s docs say neither OpenAI nor the payment providers take the merchant-of-record role (merchant-of-record); Stripe’s Shared Payment Token is the first implementation OpenAI names (delegated-payment)OpenAI’s ACP docs said so before OpenAI rewrote them between 2026-11-12 and 2026-11-13; the rewritten docs no longer describe delegated payment, though OpenAI’s plugin Checkout API reference still points PCI DSS Level 1 merchants to Delegate Payment (2026-11-14), and the ACP website names Stripe, with its SPT, as the first compatible payment service providerOpenAI’s Agentic Commerce docs as archived on 2026-11-07 (Internet Archive), before the rewrite; Agentic Commerce Protocol website (OpenAI and Stripe); OpenAI plugin Checkout API reference (2026-11-14)glossary merchant-of-record and delegated-payment
F121Four papers listed as not peer reviewed (Gong, Ranjan, Chard, Xue); the Piet paper titled Plan-Then-Execute, with 80 percent of WebArena tasks runnable as pure programsEach of the four has a peer-reviewed version with a DOI: MDPI Systems 14(10) under a new title (Gong), IEEE BCC 2025 (Ranjan), IEEE eScience 2026 (Chard) and ACM CCS 2026 (Xue); version 2 of arXiv 2605.14290 (2026-10-23) is titled Compile-and-Execute and gives 81 percentCrossref records for DOIs 10.3390/systems14101329, 10.1109/BCC63751.2025.11725761, 10.1109/eScience70237.2026.00090 and 10.1145/3830454.3846774; arXiv 2605.14290v2publications pub-gong-2026-ais, pub-ranjan-2025-loka, pub-chard-2026-cairn, pub-xue-2026-zkmldebloat, pub-piet-2026-plan
F122Smaller cross-site corrections: the mppx SDK offers optional request attestation for Web Bot Auth and TAP; ANP’s status is Draft, with no relations; three efforts carry the KYA label; KYAPay’s current revision is -02 of 2026-10-02; ANSv2’s latest revision is -01, with Bronze, Silver and Gold tiers; SD-JWT VC -19 sits with the IESG awaiting the area director; Klarna’s protocol covers 12 markets; PayPal’s Agent Ready payments were slated for early 2026; the global timeline’s 2026-10-11 Market event says x402.org still shows 75.41M transactions and $24.24M for the last 30 daysSince mppx 0.16.0 (2026-10-28) Web Bot Auth and TAP are among its per-route identity verifiers and provers; ANP 1.2 was released on 2026-09-24 (V1.0 on 2025-05-19), and its draft ANP-10 adapts AP2 v0.1 (lineage); DIF’s KYA-OS (2026-04-22) is a fourth effort; KYAPay -03 (2026-11-02); ANSv2 -02 (2026-10-26) has badge and SCITT tiers; SD-JWT VC -26 (2026-11-06) is in IESG evaluation, not approved; 13 markets, per Klarna’s release of 2025-12-15; PayPal’s Agent Ready docs list ACP for ChatGPT with Braintree delegated tokens and UCP for Google AI Mode and Gemini through the Google Pay handler (2026-11-14); x402.org still showed those values under its Last 30 Days counter on 2026-10-11, and the counter was gone by 2026-11-14wevm mppx CHANGELOG; ANP releases and ANP-10 on GitHub; DIF KYA-OS announcement (2026-04-22); IETF Datatracker for KYAPay -03, ANSv2 -02 and SD-JWT VC -26; Klarna newsroom release (2025-12-15); PayPal Agent Ready overview (2026-11-14); x402.org (read 2026-11-14) and its Internet Archive capture of 2026-10-24orbit web-bot-auth and rfc-9421-9530 (stripe-mpp relation notes and body), anp, know-your-agent, agent-name-service-nanda, verifiable-credentials, klarna-app, paypal-agentic; research/market.json Market-lane event 2026-10-11 (global timeline)

Visitor statistics

The site counts page views with Cloudflare Web Analytics. Cloudflare adds a small script to each page at its edge. The script sets no cookies and stores nothing in your browser (external link), and Cloudflare discards the IP address at the nearest data center (external link). It reports page views, visits, referring sites, countries, browsers and load times, not individual readers. Crawler and AI assistant counts come from Cloudflare's records of requests at its edge and add nothing to the page. Your notes and settings stay in this browser.

Source details

    Loading the index.

    Enter open Esc close ? shortcuts