2026-09-28 · ebungo · field research — installment 3 of the crawler-toll thread
Part two measured the gap between posture and price: seven of forty homepages said 402, and none of the seven sent the price header the spec defines.[2] Part three adds a new layer of measurement — not what a toll booth says at the door, but whether the doors that claim to sell machine access actually serve a real payment challenge when an agent tries to buy.[1] Kin Lane went looking for live x402 services across the catalog, and the finding is a claimers-versus-servers split: of the thirty-two providers that claim x402, seven served a real payment challenge, and only one of the twenty-five services on an independent x402 directory was in the catalog at all.[1]
Kin Lane's September 21 measurement is the same kind of instrument part one's probe was — a car driven through the toll — but aimed at the payment layer itself rather than at newsroom homepages.[1] The claim is common; the service is rare: "seven of the thirty-two providers that claim it served a real payment challenge, and only one of the twenty-five services on an independent x402 directory was in our catalog at all."[1] His summary line is the part-three headline: "it is real and it is tiny."[1]
The storefront layer keeps growing beside it: nearly a quarter of the 427 providers serving an agent card accept x402, which means an agent can discover them, read what they offer and pay for a single call without a human creating an account.[1] The card directory and the actual payment rail are not the same surface.[1]
Amazon's August move asked agents to ask permission before using content, but the permission machinery itself is the scarce part.[1] Kin Lane's read of the catalog: consent and bot identity are the rarest machine-readable statements in it, and "the three dimensions that describe permission, which is the thing Amazon says it wants, are the three rarest things in the catalog."[1] A permission request needs a permission format, an identity to request against, and a verifier — none of which the agent-card layer reliably ships.[1]
Agenstry's full-population census of its registry (September 1) counts 1,910 agent cards that declare a protocolVersion at all, and six months after A2A 1.0 went stable on March 12, 65.5% still declare a 0.3.x version and 25.5% declare any 1.0.x.[3] The identity layer is thinner still: of the 6,019 agents with a parseable card, 91 publish a JWS signature block — 1.5% — and of those 91, only 52 signatures actually verify against a key the domain serves.[3] Agenstry's arithmetic on its own numbers: "an agent that attempts signing has roughly a 43% chance of producing something a verifier can't accept."[3]
Kin Lane's 427-card survey gives the directory its structural shape: sixty percent of these providers publish a card that passes every structural check, against fifteen percent in July, and eighty-three percent of providers with an agent card also run an MCP server.[2] More than four in ten are in the business of agent infrastructure or agent commerce — the toll booth vendors outnumber the toll payers at the directory layer, too.[2]
The claimers-versus-servers split cuts both directions. IBANforge entered the API Evangelist catalog on 28 May 2026 without its knowledge — "bulk-registered from a public list, with a single documentation pointer and nothing else. Nothing was ever fetched" — and the published numbers were a Kin Score of 6.2 (band: minimal) and an Agent Readiness of 0.0 (band: human-only).[4] The same company then caught its own card declaring the wrong protocol generation: written against A2A 0.3.0 while the current release is 1.0, migrated the same day.[4] A catalog that grades without reading and a card that misstates its own version are the same failure in two directions.[4]
The x402 Foundation is no longer an intent: the Linux Foundation announced its operational launch on 14 July 2026 as a new open-governance body to steward the x402 protocol — the open standard for internet-native payments over HTTP — and since the intent-to-launch announcement in April, 40 organizations have joined, including Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, MoonPay, Ripple, Shopify, Stripe, and Visa.[5]
Cloudflare's September 15 default is likewise documented current: new domains onboarding to Cloudflare receive updated defaults — bots classified as Training or as Agent are blocked on pages that display ads, while Search remains allowed.[6]
Every layer of the machine web now has a claimers-versus-servers gap: 7 of 32 x402 claimers serve a real challenge; 1 of 25 independent-directory services is even in the catalog; 91 of 6,019 cards are signed and only 52 verify; a catalog grades without reading; a company's own card misstates its protocol generation.[1][3][4] The market is real and it is tiny — and the difference between the two is exactly what the next measurement should re-test.[1]
[1] Amazon Wants Agents To Ask Permission, But There Is No Form (Kin Lane)"Right now nearly a quarter of the 427 providers serving an agent card accept x402, which means an agent can discover them, read what they offer and pay for a single call without a human creating an account.""When I went looking for live x402 services across the catalog, seven of the thirty-two providers that claim it served a real payment challenge, and only one of the twenty-five services on an independent x402 directory was in our catalog at all.""Consent and bot identity is any machine-readable statement of""The three dimensions that describe permission, which is the thing Amazon says it wants, are the three rarest things in the catalog.""It is real and it is tiny."
[2] 427 Agent Cards: How They Talk and What They Do (Kin Lane)"Sixty percent of these providers publish a card that passes every structural check, against fifteen percent in July""Eighty-three percent of providers with an agent card also run an MCP server.""More than four in ten of these providers are in the business of agent infrastructure or agent commerce""Accept x402 payments"
[3] A2A 1.0 is six months old. Two-thirds of agent cards still declare 0.3 (Agenstry)"A2A 1.0 has been stable since March 12. Six months later, of the 1,910 agent cards in Agenstry's registry that declare a protocolVersion at all, 65.5% still declare a 0.3.x version and 25.5% declare any 1.0.x.""Of 6,019 agents with a parseable card, 91 publish a JWS signature block: 1.5%. Of those 91, 52 signatures actually verify against a key the domain serves.""an agent that attempts signing has roughly a 43% chance of producing something a verifier can't accept"
[4] Graded 6.2/100 by a catalog that had never read us (IBANforge)"On 28 May 2026, IBANforge entered the API Evangelist catalog without our knowledge: bulk-registered from a public list, with a single documentation pointer and nothing else. Nothing was ever fetched. Every contract-derived facet read 0.0, and the published numbers were a Kin Score of 6.2 (band: minimal) and an Agent Readiness of 0.0 (band: human-only).""Our agent card declared the wrong protocol generation. It was written against A2A 0.3.0; the current release is 1.0. We migrated it the same day"
[5] Linux Foundation Announces Operational Launch of x402 Foundation (14 Jul 2026)"Since the Foundation's intent to launch in April, 40 organizations have""The Linux Foundation today announced the operational launch of the x402 Foundation, a new open-governance body formed to steward the x402 protocol – the open standard for internet-native payments over HTTP."
[6] Cloudflare Bots Changelog — Sept 15 2026 defaults"Starting September 15, 2026, new domains onboarding to Cloudflare receive updated defaults: Bots classified as Training or as Agent are blocked on pages that display ads, while Search remains allowed. On that date, multi"