From 2d6bb0570bd1c1d9f8d81d5dac8f9064471b7a08 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 30 Oct 2026 05:38:21 +0000 Subject: [PATCH 1/2] Recheck six standards whose specs changed; move their pins The weekly spec drift watch found changes in ARD, ai-catalog, WebMCP, Web Bot Auth, Poppy and x402. Each page was rechecked against its live sources and last_verified moved to 2026-10-30. No status changes. - Poppy: version 0.2 published October 24, draft 0.3 in progress (scopes, transitional mediated sign-in, operations v2); guide.json note updated. - Web Bot Auth: WG draft -01 (October 29): Signature-Agent now names the key set's address directly, and sites can ask for a signature. Signers now link primary sources; DuckDuckGo dropped (no primary evidence). - WebMCP: draft of October 27, the draft W3C Agentic Web WG charter, the trial passing 0.5% of Chrome page loads, Hydrogen on by default. - ai-catalog: multi-party Trust Manifests; Cloudflare's catalog and the working group's list of 26. - x402: October 22 disclosure of library flaws (fixed in August); the CoinDesk figure is volume, not real payments; Foundation source linked. - ARD: only a non-normative observability section upstream; Hugging Face serves only ai-catalog.json too. Closes #16, closes #17, closes #18, closes #19. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NWyUpDcNT2Fd6FNzeuy2Bn --- content/guide.json | 2 +- content/standards/ai-catalog.md | 8 +++++--- content/standards/ard.md | 6 +++--- content/standards/poppy.md | 24 ++++++++++++------------ content/standards/web-bot-auth.md | 12 ++++++------ content/standards/webmcp.md | 14 +++++++------- content/standards/x402.md | 10 ++++++---- spec-pins.json | 16 ++++++++-------- 8 files changed, 48 insertions(+), 44 deletions(-) diff --git a/content/guide.json b/content/guide.json index 4754278..817bec1 100644 --- a/content/guide.json +++ b/content/guide.json @@ -7,7 +7,7 @@ { "situation": "You have lots of structured content people and agents want to query", "standards": ["nlweb"] }, { "situation": "Your bot visits other sites, or you need to verify bots on yours", "standards": ["web-bot-auth"] }, { "situation": "You want agents to create accounts on your service without a sign-up form", "standards": ["auth-md"] }, - { "situation": "Customers' own agents should sign in and act on their accounts", "standards": ["poppy"], "note": "Track it; Draft 0.1 is from October 9, 2026, and 0.2 is in progress." }, + { "situation": "Customers' own agents should sign in and act on their accounts", "standards": ["poppy"], "note": "Track it; Draft 0.2 is from October 24, 2026, and 0.3 is in progress." }, { "situation": "You sell goods and want any AI assistant to browse, cart and check out", "standards": ["ucp"] }, { "situation": "You want your products shown in ChatGPT", "standards": ["acp"] }, { "situation": "An agent pays and you need proof a person approved those exact terms", "standards": ["ap2"] }, diff --git a/content/standards/ai-catalog.md b/content/standards/ai-catalog.md index b69e06b..74d9571 100644 --- a/content/standards/ai-catalog.md +++ b/content/standards/ai-catalog.md @@ -11,7 +11,7 @@ analogy: Your site's table of contents for AI. looks_like: /.well-known/ai-catalog.json when_to_use: When you publish that same list for MCP Server Cards and older tools. Serve one file at both addresses. backers: Linux Foundation working group (MCP and A2A communities) -reality_check: Early, with live catalogs at GitHub, Buildkite and Hugging Face. ARD tools look for `ard.json` first and may skip the old address, so serve the same file at both `ai-catalog.json` and `ard.json`. +reality_check: Early, with live catalogs at GitHub, Buildkite, Hugging Face and Cloudflare's developer docs. [The working group's own list](https://github.com/Agent-Card/awesome-ai-catalogs) has 26, mostly small sites. ARD tools look for `ard.json` first and may skip the old address, so serve the same file at both `ai-catalog.json` and `ard.json`. links: - label: ai-catalog.io url: https://ai-catalog.io/ @@ -24,12 +24,12 @@ related: note: ARD calls ai-catalog its predecessor. ai-catalog sees itself as the lightweight publishing format; it was split off, not retired. - id: nlweb note: A catalog can list an NLWeb endpoint. -last_verified: "2026-10-19" +last_verified: "2026-10-30" spec_sources: - kind: git-path repo: Agent-Card/ai-catalog path: specification - pin: "e020b2db26f8f13e904a95e0e457457dd3da9efd" + pin: "7ee97d9655a13e1f6442ab505982c03db17134ea" --- ## How it works @@ -38,6 +38,8 @@ Like a table of contents, it doesn't contain the chapters; it tells you where ea A restaurant that works with a booking provider and a jobs provider can list both AI tools, so any assistant that only knows the restaurant's web address can find the booking tool. Catalogs can also point to other catalogs, so a big platform can list many sub-catalogs. +An entry can also carry optional Trust Manifests: claims about the tool, such as who published it or which audits it passed, each of which can be signed. Since October 6, 2026, the [spec](https://ai-catalog.io/spec/) lets several parties, say the publisher and an auditor, each add their own. + ## Who's behind it It's developed in a [Linux Foundation working repository](https://github.com/Agent-Card/ai-catalog) (started October 2025) with members from the MCP and A2A communities, and published at [ai-catalog.io](https://ai-catalog.io/). Even the group's name is inconsistent: ai-catalog.io calls it the "Agent Card Working Group," while Google thanks the "AI Catalog Working Group." diff --git a/content/standards/ard.md b/content/standards/ard.md index 039ac04..db81b5f 100644 --- a/content/standards/ard.md +++ b/content/standards/ard.md @@ -11,7 +11,7 @@ analogy: A search engine for agent tools. looks_like: /.well-known/ard.json when_to_use: When you offer APIs, MCP servers or agents and want agent search registries to find them. backers: Google-led authors (Google, Hugging Face, R.V. Guha) -reality_check: Early. [Hugging Face runs a public registry](https://huggingface.co/blog/agentic-resource-discovery-launch), and Hugging Face and GitHub now publish catalogs, though GitHub's is only at the older `ai-catalog.json` address. According to [an independent sweep in September 2026](https://github.com/Agent-Card/ai-catalog/issues/115), only 24 of 102 publishers could be found at `ard.json`; the other 78 used only `ai-catalog.json`. +reality_check: Early. [Hugging Face runs a public registry](https://huggingface.co/blog/agentic-resource-discovery-launch), and Hugging Face and GitHub now publish catalogs, though both only at the older [`ai-catalog.json`](https://huggingface.co/.well-known/ai-catalog.json) address. According to [an independent sweep in September 2026](https://github.com/Agent-Card/ai-catalog/issues/115), only 24 of 102 publishers could be found at `ard.json`; the other 78 used only `ai-catalog.json`. links: - label: Specification (v0.91) url: https://agenticresourcediscovery.org/spec/ @@ -22,12 +22,12 @@ links: related: - id: ai-catalog note: Its predecessor, now the publishing format. ARD is the discovery format. Serve the same file at both addresses. -last_verified: "2026-10-19" +last_verified: "2026-10-30" spec_sources: - kind: git-path repo: ards-project/ard-spec path: spec - pin: "40151d4a76af2e266723f78d9142f54a89fb5dcf" + pin: "eca2857d0c9b7b27aa2fb72fe3bb69fcd0d18ea9" --- ## How it works diff --git a/content/standards/poppy.md b/content/standards/poppy.md index 8a02469..40ce5f0 100644 --- a/content/standards/poppy.md +++ b/content/standards/poppy.md @@ -4,7 +4,7 @@ full_name: Personal Agent Protocol (PAP) job: identity order: 2 status: early -status_note: Draft 0.1 (Oct 9, 2026), 0.2 in progress; a few small deployments +status_note: Draft 0.2 (Oct 24, 2026), 0.3 in progress; a few small deployments tagline: acts as you phrase: Your agent signs in to a company as you analogy: A valet key for your personal agent. @@ -13,9 +13,9 @@ when_to_use: When customers' own agents should sign in and act on their accounts backers: Sierra + Meta; 7 launch and 35 design partners reality_check: A draft first published October 9, 2026. A few small companies serve a `poppy.json`, including [Salespeak](https://salespeak.ai/agent-endpoint/), [Lorikeet](https://www.lorikeetcx.ai/blog/personal-agent-protocol), [Ticket Fairy](https://www.ticketfairy.com/.well-known/poppy.json) and [Alpic](https://alpic.ai/.well-known/poppy.json), most for signed-out chats or plain website browsing only. None of the launch partners does yet. links: - - label: Specification (Draft 0.1) - url: https://personalagentprotocol.org/docs/0.1/spec - - label: Draft 0.2 (in progress) + - label: Specification (Draft 0.2) + url: https://personalagentprotocol.org/docs/0.2/spec + - label: Draft 0.3 (in progress) url: https://personalagentprotocol.org/docs/spec - label: Path to 1.0 (open topics) url: https://personalagentprotocol.org/docs/path-to-1 @@ -34,29 +34,29 @@ related: note: Poppy leaves shopping to UCP and ACP, and may overlap with UCP on sign-in. - id: ap2 note: Payments are not covered yet. Until they are, payment consent needs another protocol, such as AP2. -last_verified: "2026-10-19" +last_verified: "2026-10-30" spec_sources: - kind: page url: https://personalagentprotocol.org/docs/spec - pin: "3b7a81416cfc5f98d4ce1d6f2cb0e359cbf68a46d5a5317b5a4a856855eb50e3" + pin: "24d8da14fd16c944adeb9969221e6d6a6d9ba089f7299ce8c6a8df8a860001f3" - kind: page url: https://personalagentprotocol.org/docs/extensions/operations - pin: "6f94925f7306c2d19cb5548e9655c8d414709301ba8ef37c6e1a436969614b7f" + pin: "ec14d1af5ac4a65e0f691e49fbdf57ede32f32552d86ed88865e85bf8eedb169" - kind: page url: https://personalagentprotocol.org/docs/guides - pin: "f2b0a17c0f420732a721f2843717015cb3f8277fc365a6b829af5e36bd67ea49" + pin: "708fc192545d0a65b596c8dbee038338fe559f21f4d3c203023304a1168420d0" --- ## How it works It lets the agent act for you at a company, with only the permissions you gave it, without opening the boot or the glovebox. Right now an AI agent acting for you has two bad options: pretend to be you in a browser, or not get in at all. -Poppy gives the company a file at `/.well-known/poppy.json` that says how agents can start a session, how you sign in, and which web pages, APIs and company agent are available. Sign-in uses OAuth, the familiar "Sign in with..." approval screen: you approve on the company's own page, on another device with a code, or (if the company allows it) the agent signs in for you. An agent can also start signed out, as a guest. +Poppy gives the company a file at `/.well-known/poppy.json` that says how agents can start a session, how you sign in, and which web pages, APIs and company agent are available. Sign-in uses OAuth, the familiar "Sign in with..." approval screen: you approve on the company's own page, on another device with a code, or (if the company allows it) the agent signs in for you. [Draft 0.3](https://personalagentprotocol.org/docs/guides) calls that last way temporary, with an end date to be set at version 1.0. An agent can also start signed out, as a guest. -Permissions are simple scopes like "read" and "write," plus custom ones such as "manage saved addresses." You also get a different anonymous ID at each company, so companies can't match you with each other. In the launch demo, Meta's Muse agent found Rocket Mortgage's agent and, with the user's permission, completed a mortgage pre-approval. +Permissions are scopes. Version 0.2 has two shared ones, "read" and "write," and companies can add their own, such as "manage saved addresses." [Draft 0.3](https://personalagentprotocol.org/docs/changelog) drops the shared ones: each company names its own and says which make changes that can't be undone. For an action such as exchanging an item, the company can also [ask you to approve the exact terms](https://personalagentprotocol.org/docs/extensions/operations) before it acts. You also get a different anonymous ID at each company, so companies can't match you with each other. In the launch demo, Meta's Muse agent found Rocket Mortgage's agent and, with the user's permission, completed a mortgage pre-approval. ## Who's behind it -[Sierra](https://sierra.ai/blog) (led by Bret Taylor and Clay Bavor) and Meta announced it on October 6, 2026. [Sierra published Draft 0.1](https://sierra.ai/blog/poppy) on October 9 with seven launch partners (Genesys, Instinct, NiCE, Rocket, Shopify, Stripe and Walmart) and 35 more design partners, including OpenAI, Visa, Mastercard and PayPal. [Draft 0.2](https://personalagentprotocol.org/docs/changelog) is in progress, with no publication date yet. +[Sierra](https://sierra.ai/blog) (led by Bret Taylor and Clay Bavor) and Meta announced it on October 6, 2026. [Sierra published Draft 0.1](https://sierra.ai/blog/poppy) on October 9 with seven launch partners (Genesys, Instinct, NiCE, Rocket, Shopify, Stripe and Walmart) and 35 more design partners, including OpenAI, Visa, Mastercard and PayPal. [Version 0.2](https://personalagentprotocol.org/docs/0.2/spec) followed on October 24, and [draft 0.3](https://personalagentprotocol.org/docs/changelog) is in progress. -The spec warns that any part can change, even in ways that break compatibility, and [lists payments as not yet covered](https://personalagentprotocol.org/docs/path-to-1). A reference implementation was promised within about a month of October 9 and isn't out yet. An implementation kit for companies was added on October 17: a skill that has a coding agent design and build a company's side, and a validator that acts as a test agent against a deployment. It reuses OAuth, OpenAPI and MCP rather than replacing them. +The spec warns that any part can change, even in ways that break compatibility, and [lists payments as not yet covered](https://personalagentprotocol.org/docs/path-to-1). A reference implementation was promised within about a month of October 9 and isn't out yet. An implementation kit for companies was added on October 17: a skill that has a coding agent design and build a company's side, and a validator that acts as a test agent against a deployment. [The kit](https://personalagentprotocol.org/kit/company) now follows draft 0.3, not the published 0.2. Poppy reuses OAuth, OpenAPI and MCP rather than replacing them. diff --git a/content/standards/web-bot-auth.md b/content/standards/web-bot-auth.md index f4c972f..6cb2e2e 100644 --- a/content/standards/web-bot-auth.md +++ b/content/standards/web-bot-auth.md @@ -3,7 +3,7 @@ name: Web Bot Auth job: identity order: 1 status: production -status_note: WG draft -00 (Sept 1, 2026); live signers +status_note: WG draft -01 (Oct 29, 2026); live signers tagline: which bot is it phrase: Cryptographic ID for bots analogy: A tamper-proof ID badge for bots, instead of a name tag anyone could write. @@ -23,18 +23,18 @@ related: note: auth.md signs up a new user for the agent; Web Bot Auth only proves which bot is asking. - id: x402 note: Cloudflare plans to use them together for pay-per-crawl. -last_verified: "2026-10-19" +last_verified: "2026-10-30" spec_sources: - kind: ietf-draft name: draft-ietf-webbotauth-httpsig-protocol - pin: "00" + pin: "01" --- ## How it works -Today websites identify bots by a label (the "user agent") that anyone can fake, or by IP address, which breaks easily. With Web Bot Auth, the company running the bot publishes a public key at a well-known address and signs every request with the matching private key, using an existing IETF standard for signing web requests (RFC 9421). +Today websites identify bots by a label (the "user agent") that anyone can fake, or by IP address, which breaks easily. With Web Bot Auth, the company running the bot publishes its public keys at a web address, names that address in each request, and signs the request with the matching private key, using an existing IETF standard for signing web requests (RFC 9421). -The website, or its CDN such as Cloudflare, checks the signature and knows for certain "this really is OpenAI's agent" before deciding to let it in, block it or charge it. A news site can let a verified shopping agent through while stopping an anonymous scraper wearing the same label. +The website, or its CDN such as Cloudflare, checks the signature and knows for certain "this really is OpenAI's agent" before deciding to let it in, block it or charge it. A site can also ask an unsigned bot to sign. A news site can let a verified shopping agent through while stopping an anonymous scraper wearing the same label. It answers *which agent* is visiting, not *whom it represents*; that's Poppy's and OAuth's job. @@ -42,4 +42,4 @@ It answers *which agent* is visiting, not *whom it represents*; that's Poppy's a Cloudflare proposed it in May 2025. On September 1, 2026 the IETF's webbotauth working group [adopted it as an official working-group draft](https://datatracker.ietf.org/doc/draft-ietf-webbotauth-httpsig-protocol/), written by authors from Cloudflare and Google; it's the group's only adopted document. It's still a draft, not an RFC: adoption isn't approval. -[Visa's Trusted Agent Protocol and Mastercard's Agent Pay build on it](https://blog.cloudflare.com/secure-agentic-commerce/), adding a tag that says whether the agent is browsing or buying, and observers report OpenAI, Cloudflare and DuckDuckGo signing requests today. The working-group draft has already changed how a request points to its key directory, but [Cloudflare's own checker](https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/) still expects the older format (as of October 8, 2026), so early implementations may need updates. +[Visa's Trusted Agent Protocol and Mastercard's Agent Pay build on it](https://blog.cloudflare.com/secure-agentic-commerce/), adding a tag that says whether the agent is browsing or buying. [OpenAI's ChatGPT agent](https://help.openai.com/en/articles/11845367), [Cloudflare's Browser Run](https://developers.cloudflare.com/browser-run/reference/automatic-request-headers/) and, as an experiment, [some Google-Agent traffic](https://developers.google.com/crawling/docs/crawlers-fetchers/web-bot-auth) sign requests today. [Revision -01](https://datatracker.ietf.org/doc/html/draft-ietf-webbotauth-httpsig-protocol-01) (October 29, 2026) changed how a request points to its keys: it now gives the exact address of its key set. [Cloudflare's own checker](https://developers.cloudflare.com/bots/reference/bot-verification/web-bot-auth/) still expects the older format (as of October 8, 2026), so early implementations will need updates. diff --git a/content/standards/webmcp.md b/content/standards/webmcp.md index 4280b2b..e2ac87f 100644 --- a/content/standards/webmcp.md +++ b/content/standards/webmcp.md @@ -3,7 +3,7 @@ name: WebMCP job: act order: 1 status: early -status_note: Draft (Oct 16, 2026); Chrome and Edge trials; live in ChatGPT desktop and Shopify +status_note: Draft (Oct 27, 2026); Chrome and Edge trials; live in ChatGPT desktop and Shopify tagline: page tools phrase: A page hands typed tools to the agent in your browser analogy: A labeled menu of actions for the agent in your browser. @@ -12,7 +12,7 @@ when_to_use: When agents use your site in people's browsers. Add tools to your k backers: W3C Web ML community group; Microsoft and Google editors reality_check: Early use with two big real-world users, ChatGPT's desktop browser and Shopify, while Chrome and Edge are still in trials. links: - - label: Draft (Oct 16, 2026) + - label: Draft (Oct 27, 2026) url: https://webmachinelearning.github.io/webmcp/ - label: Chrome docs url: https://developer.chrome.com/docs/ai/webmcp @@ -23,12 +23,12 @@ related: note: NLWeb is an endpoint on your server. WebMCP works inside the browser page. - id: ucp note: Shopify puts WebMCP tools on every Liquid storefront, next to its UCP support. -last_verified: "2026-10-19" +last_verified: "2026-10-30" spec_sources: - kind: git-path repo: webmachinelearning/webmcp path: index.bs - pin: "bd81b6d06c4d22bd15c14849030bbeb2fb14d9cd" + pin: "ce879543a9013dae3effe292e6deda0b4323a07d" --- ## How it works @@ -41,11 +41,11 @@ One caveat: a page's tool descriptions are text the AI reads, so a malicious sit ## Who's behind it -Microsoft and Google proposed it together in August 2025; the W3C's Web Machine Learning community group took it up that September, with editors from both companies. The current text is a [draft dated October 16, 2026](https://webmachinelearning.github.io/webmcp/) that says plainly it is "not a W3C Standard." +Microsoft and Google proposed it together in August 2025; the W3C's Web Machine Learning community group took it up that September, with editors from both companies. The current text is a [draft dated October 27, 2026](https://webmachinelearning.github.io/webmcp/) that says plainly it is "not a W3C Standard." A [draft W3C charter](https://w3c.github.io/charter-drafts/2026/agenticweb-wg.html) for a new Agentic Web Working Group would take WebMCP as its starting text, but that group does not exist yet. -[Chrome has been testing it](https://developer.chrome.com/docs/ai/webmcp) in a time-limited "origin trial" (Chrome 149-156) since May 2026; on September 28 [Google asked to extend the trial](http://www.mail-archive.com/blink-dev@chromium.org/msg17568.html) to Chrome 162 because feedback is still changing the API, so there's no ship date. [Edge runs its own trial](https://developer.microsoft.com/en-us/microsoft-edge/origin-trials/trials/0b76fe60-b266-458e-a285-04e375c0c31a) (through March 30, 2027) and [calls it "ready for testing."](https://blogs.windows.com/msedgedev/2026/09/21/new-in-edge-for-developers-create-better-components-and-make-your-site-agent-ready/) +[Chrome has been testing it](https://developer.chrome.com/docs/ai/webmcp) in a time-limited "origin trial" (Chrome 149-156) since May 2026; on September 28 [Google asked to extend the trial](http://www.mail-archive.com/blink-dev@chromium.org/msg17568.html) to Chrome 162 because feedback is still changing the API, so there's no ship date. On October 28, Google said [pages using the trial had passed 0.5% of all Chrome page loads](http://www.mail-archive.com/blink-dev@chromium.org/msg17895.html), though agents call the tools far less often. [Edge runs its own trial](https://developer.microsoft.com/en-us/microsoft-edge/origin-trials/trials/0b76fe60-b266-458e-a285-04e375c0c31a) (through March 30, 2027) and [calls it "ready for testing."](https://blogs.windows.com/msedgedev/2026/09/21/new-in-edge-for-developers-create-better-components-and-make-your-site-agent-ready/) -[ChatGPT's desktop browser calls these "site tools"](https://help.openai.com/en/articles/20001423-using-site-tools-in-the-chatgpt-desktop-app) automatically, and [Shopify puts WebMCP tools on every Liquid storefront](https://shopify.dev/docs/api/web-mcp) (Hydrogen stores can turn them on), including a [checkout tool that agents may only call after the buyer approves the order and total](https://shopify.dev/docs/agents/carts-and-checkout/checkout-webmcp). [Safari's team opposes it](https://github.com/WebKit/standards-positions/issues/670) and [Firefox is neutral](https://github.com/mozilla/standards-positions/issues/1412). +[ChatGPT's desktop browser calls these "site tools"](https://help.openai.com/en/articles/20001423-using-site-tools-in-the-chatgpt-desktop-app) automatically, and [Shopify puts WebMCP tools on every Liquid storefront](https://shopify.dev/docs/api/web-mcp) (and on Hydrogen stores from the 2026-10 release, unless turned off), including a [checkout tool that agents may only call after the buyer approves the order and total](https://shopify.dev/docs/agents/carts-and-checkout/checkout-webmcp). [Safari's team opposes it](https://github.com/WebKit/standards-positions/issues/670) and [Firefox is neutral](https://github.com/mozilla/standards-positions/issues/1412). ## Neighbours diff --git a/content/standards/x402.md b/content/standards/x402.md index 2411a02..cff03e7 100644 --- a/content/standards/x402.md +++ b/content/standards/x402.md @@ -10,7 +10,7 @@ analogy: A parking meter on every web page. Drop in a few cents and the gate ope looks_like: 402 Payment Required when_to_use: When you charge per API request in stablecoins, with no accounts or sign-up. backers: Coinbase, now the x402 Foundation (Linux Foundation) -reality_check: In production, but small. [TRM Labs (September 9, 2026)](https://www.trmlabs.com/trm-tech-blog/whos-actually-paying-measuring-ai-agent-payments-onchain) counted 198.9 million settlements worth $52.7 million since May 2025. After removing self-payments and similar flows, about $25.6 million looked like real commerce, and only 0.6% to 7.5% of that seemed to come from AI agents. Earlier, [CoinDesk (March 11, 2026)](https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) found about $28,000 a day of real payments, averaging about 20 cents. [Cloudflare's "billion 402 responses a day"](https://blog.cloudflare.com/x402/) counts payment *requests*, not payments. Count dollars, not transactions. +reality_check: In production, but small. [TRM Labs (September 9, 2026)](https://www.trmlabs.com/trm-tech-blog/whos-actually-paying-measuring-ai-agent-payments-onchain) counted 198.9 million settlements worth $52.7 million since May 2025. After removing self-payments and similar flows, about $25.6 million looked like real commerce, and only 0.6% to 7.5% of that seemed to come from AI agents. Earlier, [CoinDesk (March 11, 2026)](https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) found only about $28,000 a day in volume, averaging about 20 cents, much of it testing or "gamed" transactions. [Cloudflare's "billion 402 responses a day"](https://blog.cloudflare.com/x402/) counts payment *requests*, not payments. Count dollars, not transactions. links: - label: Specification (V2) url: https://github.com/x402-foundation/x402/blob/main/specs/x402-specification-v2.md @@ -25,12 +25,12 @@ related: note: AP2 can settle through x402. - id: web-bot-auth note: Cloudflare plans to use them together for pay-per-crawl. -last_verified: "2026-10-19" +last_verified: "2026-10-30" spec_sources: - kind: git-path repo: x402-foundation/x402 path: specs - pin: "fd92aa2f26e0b20985479ef43ab54cb28b555cf2" + pin: "11f02ce95e15d78e246efcbd5253ecbeefc2718d" --- ## How it works @@ -39,6 +39,8 @@ The internet never had a built-in way to charge tiny amounts, so content is eith Picture an agent paying a weather API a cent per lookup, or a crawler paying a publisher per page instead of being blocked. +Keep the official code libraries up to date. On October 22, 2026 a security firm [reported three critical flaws](https://v12.sh/blog/x402) in them, including no default spending cap, so a hostile server could ask for a wallet's whole balance. Fixes shipped in August. + ## Who's behind it -Coinbase created it, and [version 2 shipped on December 11, 2025](https://x402.org/x402-v2-launch/). The Linux Foundation announced an x402 Foundation on April 2, 2026 and [made it operational on July 14](https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications) with 40 members. It now [lists 57](https://www.x402.org/members); the 19 premier members include AWS, Google, Visa, Mastercard, American Express, PayPal, Stripe, Shopify, Cloudflare, Coinbase and Circle, the broadest coalition of any agent-payment standard. +Coinbase created it, and [version 2 shipped on December 11, 2025](https://x402.org/x402-v2-launch/). The Linux Foundation [announced an x402 Foundation on April 2, 2026](https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol) and [made it operational on July 14](https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications) with 40 members. It now [lists 57](https://www.x402.org/members); the 19 premier members include AWS, Google, Visa, Mastercard, American Express, PayPal, Stripe, Shopify, Cloudflare, Coinbase and Circle. diff --git a/spec-pins.json b/spec-pins.json index 243d2e1..4b1102f 100644 --- a/spec-pins.json +++ b/spec-pins.json @@ -16,7 +16,7 @@ "kind": "git-path", "repo": "ards-project/ard-spec", "path": "spec", - "pin": "40151d4a76af2e266723f78d9142f54a89fb5dcf" + "pin": "eca2857d0c9b7b27aa2fb72fe3bb69fcd0d18ea9" } ] }, @@ -29,7 +29,7 @@ "kind": "git-path", "repo": "Agent-Card/ai-catalog", "path": "specification", - "pin": "e020b2db26f8f13e904a95e0e457457dd3da9efd" + "pin": "7ee97d9655a13e1f6442ab505982c03db17134ea" } ] }, @@ -42,7 +42,7 @@ "kind": "git-path", "repo": "webmachinelearning/webmcp", "path": "index.bs", - "pin": "bd81b6d06c4d22bd15c14849030bbeb2fb14d9cd" + "pin": "ce879543a9013dae3effe292e6deda0b4323a07d" } ] }, @@ -67,7 +67,7 @@ { "kind": "ietf-draft", "name": "draft-ietf-webbotauth-httpsig-protocol", - "pin": "00" + "pin": "01" } ] }, @@ -79,17 +79,17 @@ { "kind": "page", "url": "https://personalagentprotocol.org/docs/spec", - "pin": "3b7a81416cfc5f98d4ce1d6f2cb0e359cbf68a46d5a5317b5a4a856855eb50e3" + "pin": "24d8da14fd16c944adeb9969221e6d6a6d9ba089f7299ce8c6a8df8a860001f3" }, { "kind": "page", "url": "https://personalagentprotocol.org/docs/extensions/operations", - "pin": "6f94925f7306c2d19cb5548e9655c8d414709301ba8ef37c6e1a436969614b7f" + "pin": "ec14d1af5ac4a65e0f691e49fbdf57ede32f32552d86ed88865e85bf8eedb169" }, { "kind": "page", "url": "https://personalagentprotocol.org/docs/guides", - "pin": "f2b0a17c0f420732a721f2843717015cb3f8277fc365a6b829af5e36bd67ea49" + "pin": "708fc192545d0a65b596c8dbee038338fe559f21f4d3c203023304a1168420d0" } ] }, @@ -171,7 +171,7 @@ "kind": "git-path", "repo": "x402-foundation/x402", "path": "specs", - "pin": "fd92aa2f26e0b20985479ef43ab54cb28b555cf2" + "pin": "11f02ce95e15d78e246efcbd5253ecbeefc2718d" } ] } From bd74f89dc5e17097e833d5506d76dadb345b2015 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 30 Oct 2026 19:54:13 +0000 Subject: [PATCH 2/2] MPP: say which rails carry which payments The example said MPP's pay-as-you-go sessions run with stablecoins or ordinary cards through Stripe. Cards through Stripe cover one-off charges only; sessions run on stablecoin rails such as Tempo (mpp.dev, and the examples in draft-httpauth-payment-01: tempo/session, stripe/charge). Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01NWyUpDcNT2Fd6FNzeuy2Bn --- content/standards/mpp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/standards/mpp.md b/content/standards/mpp.md index c88a922..79b4eab 100644 --- a/content/standards/mpp.md +++ b/content/standards/mpp.md @@ -33,7 +33,7 @@ spec_sources: Paying for an online service usually means signing up, getting a key and setting up billing, which an autonomous agent can't easily do. MPP uses the web's long-unused "402 Payment Required" code: the server replies "this costs 2 cents, here's how to pay," the client pays, and the server returns the result plus a receipt. -It supports one-off charges, subscriptions and streaming pay-as-you-go "sessions," with stablecoins on the Tempo blockchain or ordinary cards through Stripe. Picture a research agent paying a fraction of a cent per article from a paywalled archive and settling the total when it finishes. +It supports one-off charges, subscriptions and streaming pay-as-you-go "sessions." One-off charges can use ordinary cards through Stripe; sessions run on stablecoins, such as on the Tempo blockchain. Picture a research agent paying a fraction of a cent per article from a paywalled archive and settling the total when it finishes. ## Who's behind it