Orcpin Research · Monthly Snapshot
Every paid endpoint built for AI agents sees three populations: watchers (crawlers, indexers, and scanners with no purchasing capacity), evaluators (agents that read the payment challenge and do not purchase), and purchasers (wallets that settle). The middle bucket matters: an evaluator may hold a funded wallet and still decline, because its code does not authorize the purchase at that price or for that need. Wallet possession is only observable at settlement, so the buckets are defined by behavior, and low sell-through is a mix of missing wallets and agent policy saying no. Most published numbers blur all three populations together. This monthly report measures the split. It combines a full census of the listed x402 paid-endpoint universe, a daily reliability sweep across that universe, the traffic mix at Orcpin's own endpoints, and the rails landscape those wallets transact on. The report contains counts and cited sources, and it never offers advice. All materials used are listed in the References section.
Orcpin x402 endpoints measured
The agent-payments landscape is no longer one protocol. By mid-2026 every major payment network has shipped or announced an agent rail; they differ in who holds the wallet and in what an outsider can measure. Status entries are dated public announcements, not judgments of maturity.
| Rail | Backer | Settlement | Status (sourced) | Publicly measurable? |
|---|---|---|---|---|
| Link agent wallet, Shared Payment Tokens, Issuing for agents | Stripe | card rails; scoped one-time virtual cards | announced at Stripe Sessions 2026 (Stripe blog, docs) | no public per-service usage data |
| Machine Payments Protocol on Tempo | Stripe | Tempo L1 (Stripe-incubated chain), micropayment batching | mainnet live March 2026 (Forbes, Mar 2026) | chain is public; no service directory |
| Visa Intelligent Commerce / Visa Ready for agents | Visa | card rails, tokenized credentials | developer tooling incl. a CLI for bot payments (Forbes, Mar 2026) | no |
| Agent Pay + Verifiable Intent | Mastercard | card rails; agentic tokens; the up-to-$1.8B BVNK acquisition adds stablecoin settlement, completed Aug 3, 2026 (Mastercard press) | rollout through 2026 | no |
| Rail | Backer | Settlement | Status (sourced) | Publicly measurable? |
|---|---|---|---|---|
| x402 | Coinbase + Cloudflare; x402 Foundation (Linux Foundation) | USDC on Base & Solana, HTTP-402 native | Foundation launched July 14–15, 2026 with Visa, Mastercard, Amex, Stripe, Adyen, Fiserv, Shopify, Google, AWS, Cloudflare, Circle, Ripple as premier members (Linux Foundation press) | yes; the only rail with an open per-service catalog and on-chain settlement |
| Bedrock AgentCore Payments | AWS + Coinbase | x402 under the hood | announced 2026 (Coinbase blog); CloudFront x402 support GA | via x402's surfaces |
| Pay-per-crawl + x402 gateway | Cloudflare | x402 / HTTP 402 metering at the edge | gateway applications opened July 1, 2026 | aggregate only |
| L402 | Lightning community | Bitcoin Lightning, HTTP 402 | spec + niche deployments | partially (Lightning is opaque by design) |
| Rail | Backer | Settlement | Status (sourced) | Publicly measurable? |
|---|---|---|---|---|
| KYAPay / Know-Your-Agent credentials | Skyfire (+ Experian's KYA framework; Fastly edge verification) | overlay on any rail; a signed JWT identity travels with the request | IETF Internet-Draft, March 2026 (draft-skyfire-kyapayprofile) | the credential is verifiable; volume is not published |
| AP2 mandates / Verifiable Intent | Google / Mastercard | overlay: signed user-intent artifacts | specs published; adoption in progress | no |
| Endpoint reliability facts | Orcpin (the publisher of this report) | overlay on x402: unpaid liveness probes plus paid delivery verification, sold per call | live since June 2026 (published methodology) | yes; the measured facts are summarized in this report |
| Rail | Backer | Settlement | Status (sourced) | Publicly measurable? |
|---|---|---|---|---|
| Agentic Commerce Protocol (ACP) | OpenAI + Stripe | instant checkout inside ChatGPT, card rails | open spec, live merchants (Q2 2026 10-platform matrix) | no |
| UCP / Agentic Checkout | platform checkout | Q2 2026 | no | |
| Shopify Agents · Amazon Buy for Me · Klarna Agent Mode | respective platforms | closed, merchant-gated | Q2 2026 (same matrix) | no |
Two things follow from that last column. First, x402 is the only rail whose service population and settlement flows are open to independent measurement, which is why the rest of this report can exist at all; every other rail publishes announcements rather than populations. Second, every rail has independently converged on this report's exact question: how do you tell an economic agent from a bot that merely watches? The card networks answer it with Know-Your-Agent identity credentials, and x402 answers it with per-service payer telemetry. The mechanisms differ, but the dichotomy is the same.
Orcpin sells x402 endpoints, which makes it a measurement instrument: every arrival is classified by coarse visitor class only, and no addresses, parameters, or identities are stored (see /privacy). The chart shows each population's share of Orcpin's daily requests over the 14 days ending August 4. Shares rather than counts are deliberate: the shape of the funnel is the finding, and purchasing volume at a single seller is proprietary.
More than 999 of every 1,000 daily requests are non-economic. The watching layer includes hundreds of daily probes for /.env and similar secrets paths, which are background internet noise that every public host sees and have no relationship to the agent economy at all. The evaluator layer is more interesting: about 1,800 times a day, something reads a paid endpoint's price and terms. A 402 challenge is free to read by design, so evaluation costs nothing, and the probe does not say whether the evaluator could have paid. Some of these callers have no wallet yet; others are funded agents whose purchasing policy rejected the offer. Either way, the economy only begins at settlement, and purchasing is the rarest event on the chart by orders of magnitude. One seller is one sample; the survey below shows the same shape across the whole listed population.
On August 5 we walked the entire CDP Bazaar catalog, reading every listed x402 resource along with Coinbase's own 30-day usage figures for each. This is the complete listed population rather than a sample.
The August walk at a glance
quality.l30DaysUniquePayers per resource.
Compared with our July 16 walk of the same catalog, the listed population fell from 25,529 to 14,595, while 30-day calls rose from 313,580 to 376,311 and sellers held nearly steady (1,117 to 1,094). The share of listings with zero recorded calls collapsed from 42.7% to 0.8%. Read together, the catalog got smaller and cleaner while activity grew, which is consistent with dead listings being pruned from the index rather than with sellers leaving. Only repeated monthly walks can show this; a single snapshot cannot.
The breadth pattern matters because discovery ranking on this rail follows unique-payer counts. That design rewards breadth of wallets over depth of usage, an incentive the academic literature has described in general form (TraceRank, arXiv 2510.27554). We publish the distribution and the definitions. The ratio column belongs next to any payer count you read, here or anywhere.
The census keeps confirming the same demand picture: what sells is what an agent cannot get without paying someone. That means walled web and social data (Twitter search, Tavily, Exa), people and company enrichment, execution and compute, and real-world goods. What does not sell is data an agent can fetch free from any public RPC. The on-chain data category holds 5,148 listings, more than a third of the catalog, yet it receives only 15% of the calls, and its usage skews heavily toward one- and two-payer listings. Supply is concentrated exactly where demand is thinnest.
Below the usage layer is a liveness layer: some listed endpoints will never see a purchase because they no longer answer at all. Our prober sweeps 500 endpoints daily with unpaid requests (reading a 402 challenge is free), rotating through 1,425 tracked endpoints:
Volume figures for agent payments arrive in tiers that differ by an order of magnitude each, and most reporting quotes the largest. The same 30 days, four ways:
The same independent analyses give the trajectory: genuine volume peaked around $5.15M/month in November 2025, bottomed around $1.19M in May 2026, and roughly doubled off that floor in June. Meanwhile the x402 Foundation launched under the Linux Foundation with every major card network as a premier member. Both facts are true at once: the purchasing economy is small, and the owners of the pipes are standardizing the meter anyway. The gap between those two facts is the industry's whole bet.
api.cdp.coinbase.com/platform/v2/x402/discovery/resources (limit 100, 146 pages) on August 5, 2026, deduplicated by resource URL. Per-resource 30-day figures are CDP's own quality fields, mirrored rather than audited. Our internal July 16 walk used the identical recipe (256 pages).accepts[].amount, excluding listings priced above $1,000/call (one listing advertises $10B/call). It overstates revenue wherever advertised calls went unsettled.GET https://orcpin.dev/research.json, which serves catalog size and fleet health only, as ecosystem aggregates.Orcpin returns counts, dates, and dollars with the governing rules quoted. It never gives advice and never assigns a score. This report is measurement of a public system, not financial, legal, or investment guidance. See /terms for acceptable use.
Every number on this page is either quoted from a cited source or computed from the census rows with one of the formulas below. The census keeps one row per listed resource, carrying CDP's own 30-day figures: payers (quality.l30DaysUniquePayers), calls (quality.l30DaysTotalCalls), and the listed price (accepts[0].amount, in 6-decimal micro units, so USD = amount ÷ 1,000,000). The machine-readable summary with these same buckets is generated by npm run census.
| Number | Calculation | Inputs / result |
|---|---|---|
| 14,595 listings | The catalog's own pagination.total at walk time. Deduplicating all pages by resource URL yields 14,597 unique rows (two URLs appear twice with differing metadata); distribution figures use the 14,597 deduplicated rows. | 14,595 reported · 14,597 unique |
| 1,094 sellers | Count of distinct accepts[0].payTo addresses across all rows. | 1,094 |
| 376,311 paid calls | Sum of calls over all rows. | 376,311 |
| 73% with ≤1 payer | Rows with payers ≤ 1, divided by all rows: 10,659 ÷ 14,597. | 73.0% |
| Payer histogram | Rows bucketed by payers: exactly 0, exactly 1, 2–5, 6–20, 21 and over. Buckets sum to 14,597. | 121 · 10,538 · 3,498 · 276 · 164 |
| ≈$40K GMV | Sum of calls × price over rows with a listed price of $1,000/call or less (the cap excludes placeholder prices; one listing advertises $10B/call). | $39,982 over 12,983 rows |
| $0.01 median price | Median of price over the 13,098 rows with a nonzero listed price. | $0.01 |
| 3,938 listings with ≥2 payers | Rows with payers ≥ 2; the ratio below is undefined at 0 payers and uninformative at 1. | 3,498 + 276 + 164 |
| Calls-per-payer buckets | For each of those rows, ratio = calls ÷ payers, bucketed at ≤1.2, ≤3, ≤20, ≤100, and over 100. | 1,410 · 1,623 · 722 · 155 · 28 |
| 1,008 organic-depth listings | Rows with payers ≥ 2 and ratio ≥ 3; their calls sum to 282,049. | 1,008 · 282,049 calls |
| 25 breadth-cluster listings | Rows with payers ≥ 50 and ratio ≤ 1.2; their calls sum to 9,509. | 25 · 9,509 calls |
| Category chart | Each row is assigned the first matching category from an ordered keyword list applied to its name, description, tags, and URL (the ordered regex list is in scripts/census.ts); calls are then summed per category. | 12 categories |
| Zero-call share, July vs August | Rows with calls = 0 divided by all rows, per edition: July 10,890 ÷ 25,529; August 121 ÷ 14,597. | 42.7% → 0.8% |
| Population shares (74% · 26% · <0.1%) | Visitor-class counters summed over July 22 to August 4 and divided by 14, then expressed as shares of all daily requests. Watchers combine crawler-class hits (2,968/day) and agent catalog reads (2,127/day); evaluators are unpaid 402 probes (1,774/day); purchasers are settled calls, whose share is below one request in a thousand. Settled-call counts are not disclosed. | shares of ≈6,870 daily requests |
| Fleet chart (213 · 259 · 28) | From the August 4 sweep of 500 probed endpoints: 213 measured healthy and 259 had under 5 samples (too few to characterize); the remaining 28 = 500 − 213 − 259 carried failure or staleness flags. | 213 + 259 + 28 = 500 |
| Volume tiers ($24M · $3M · $1.6M) | Quoted directly from the a16z crypto / Allium / Artemis analysis (see References); not computed by us. The $0.04M bar is the GMV estimate above. | cited |
api.cdp.coinbase.com/platform/v2/x402/discovery/resources. Full walks performed July 16 and August 5, 2026; per-resource 30-day usage figures are CDP's own quality fields.https://orcpin.dev/research.json.