Orcpin Research · Monthly Snapshot

The Agent Economy: Purchasing vs. Watching

August 2026 edition, published August 5, 2026 · the full-catalog survey re-runs monthly · fleet measured daily · live figures refresh from https://orcpin.dev/research.json

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

14,595
listings in the CDP Bazaar catalog
crawled Aug 5, 2026
500
endpoints probed per daily sweep
1,425 tracked in rotation
213
measure healthy right now
last sweep Aug 4, 2026
$0.01
median listed price per call
August survey figure

The Rails Where Agents Transact

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.

Card Rails: The User Delegates a Wallet to the Agent

RailBackerSettlementStatus (sourced)Publicly measurable?
Link agent wallet, Shared Payment Tokens, Issuing for agentsStripecard rails; scoped one-time virtual cardsannounced at Stripe Sessions 2026 (Stripe blog, docs)no public per-service usage data
Machine Payments Protocol on TempoStripeTempo L1 (Stripe-incubated chain), micropayment batchingmainnet live March 2026 (Forbes, Mar 2026)chain is public; no service directory
Visa Intelligent Commerce / Visa Ready for agentsVisacard rails, tokenized credentialsdeveloper tooling incl. a CLI for bot payments (Forbes, Mar 2026)no
Agent Pay + Verifiable IntentMastercardcard rails; agentic tokens; the up-to-$1.8B BVNK acquisition adds stablecoin settlement, completed Aug 3, 2026 (Mastercard press)rollout through 2026no

Stablecoin Rails: The Agent Holds Its Own Wallet

RailBackerSettlementStatus (sourced)Publicly measurable?
x402Coinbase + Cloudflare; x402 Foundation (Linux Foundation)USDC on Base & Solana, HTTP-402 nativeFoundation 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 PaymentsAWS + Coinbasex402 under the hoodannounced 2026 (Coinbase blog); CloudFront x402 support GAvia x402's surfaces
Pay-per-crawl + x402 gatewayCloudflarex402 / HTTP 402 metering at the edgegateway applications opened July 1, 2026aggregate only
L402Lightning communityBitcoin Lightning, HTTP 402spec + niche deploymentspartially (Lightning is opaque by design)

Identity & Trust Overlays: Who Is This Agent?

RailBackerSettlementStatus (sourced)Publicly measurable?
KYAPay / Know-Your-Agent credentialsSkyfire (+ Experian's KYA framework; Fastly edge verification)overlay on any rail; a signed JWT identity travels with the requestIETF Internet-Draft, March 2026 (draft-skyfire-kyapayprofile)the credential is verifiable; volume is not published
AP2 mandates / Verifiable IntentGoogle / Mastercardoverlay: signed user-intent artifactsspecs published; adoption in progressno
Endpoint reliability factsOrcpin (the publisher of this report)overlay on x402: unpaid liveness probes plus paid delivery verification, sold per calllive since June 2026 (published methodology)yes; the measured facts are summarized in this report

Orchestration & Walled Gardens: The Platform Holds Everything

RailBackerSettlementStatus (sourced)Publicly measurable?
Agentic Commerce Protocol (ACP)OpenAI + Stripeinstant checkout inside ChatGPT, card railsopen spec, live merchants (Q2 2026 10-platform matrix)no
UCP / Agentic CheckoutGoogleplatform checkoutQ2 2026no
Shopify Agents · Amazon Buy for Me · Klarna Agent Moderespective platformsclosed, merchant-gatedQ2 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.

The Three Populations, Measured at Orcpin

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.

Share of Orcpin's daily requests, by population
watcherscrawlers, indexers, scannerswatchers: 74%74%evaluatorsread the 402, no purchaseevaluators: 26%26%purchaserssettled a paymentpurchasers: <0.1%<0.1%
Watchers are crawlers, indexers, uptime monitors, and vulnerability scanners, plus agent-class reads of the free catalog surfaces. Evaluators are unpaid requests to paid endpoints that received the 402 payment challenge and did not purchase. An unpaid probe reveals nothing about whether the caller holds a wallet, so this layer mixes wallet-less agents with funded agents whose code declined the purchase. Purchasers settled a payment; their share of requests is below one in a thousand, and settled-call counts are not disclosed. Shares are 14-day means ending August 4, 2026.

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.

The Purchasing Layer, Surveyed

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

14,595
listed resources
1,094 distinct sellers
376,311
paid calls, 30 days
across the whole catalog
73%
listings with ≤1 unique payer
10,659 of 14,595
≈$40K
est. 30-day GMV at list prices
junk-priced listings excluded
Unique payers per listing over 30 days, across all 14,595 listed resources
02,5005,0007,50010,0000 payers: 1211210 payers1 payer: 10,53810,5381 payer2–5: 3,4983,4982–56–20: 2762766–2021+: 16416421+
The purchasing layer is thin: 73% of listings saw at most one unique payer in 30 days, and 440 listings (3%) saw more than five. Source: census edition 2026-08-05, CDP's own quality.l30DaysUniquePayers per resource.

Compared to July

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.

Depth Versus Breadth

Calls per unique payer, for the 3,938 listings with ≥2 payers
05001,0001,500≈1 (≤1.2): 1,4101,410≈1 (≤1.2)1.2–3: 1,6231,6231.2–33–20: 7227223–2020–100: 15515520–100100+: 2828100+
The calls-per-payer ratio separates depth, where the same wallet returns for repeat use, from breadth, where many wallets each call once. 1,008 listings show organic depth (≥3 calls per payer) and carry 282,049 of the month's calls. At the other end, 25 listings combine 50+ payers with ≤1.2 calls each, totaling 9,509 calls of breadth-shaped usage. The definitions are published in the census file.

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 Paid-Endpoint Universe, Holistically

30-day paid calls by category, across all listed resources
search / web data1,719 listingssearch / web data: 208,728208,728on-chain data5,148 listingson-chain data: 56,35056,350other1,151 listingsother: 43,02943,029trading / markets2,539 listingstrading / markets: 27,59327,593inference1,017 listingsinference: 14,33614,336social335 listingssocial: 7,5177,517infra / compute523 listingsinfra / compute: 6,1726,172identity / enrichment1,186 listingsidentity / enrichment: 5,7455,745media382 listingsmedia: 2,9602,960commerce / goods259 listingscommerce / goods: 2,0632,063travel201 listingstravel: 1,0811,081storage137 listingsstorage: 737737
Categories are assigned by keyword over each listing's name, description, and tags, and the classifier is published in the census method. Walled web and search data dominates actual usage with 4× the calls of the next category, even though the on-chain data category has 3× more listings.

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.

The Endpoints That Never Participate

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:

Current measurement cycle: 500 endpoints probed
measures healthy: 213 (43%)too few samples yet: 259 (52%)flagged failing / stale: 28 (6%)measures healthy · 213 (43%)too few samples yet · 259 (52%)flagged failing / stale · 28 (6%)
This snapshot is from the August 4 sweep, and the tiles at the top of this page refresh live. Flags are raw measured states such as unreachable, consecutive failures, and stale re-verification. They are enumerated facts, never a composite score. The definitions are at orcpin.dev/methodology.

How Big Is the Purchasing Economy? A Reader's Toolkit

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 month, four measurements
headline dashboardheadline dashboard: $24M / 30d$24M / 30don-chain verifiableon-chain verifiable: $3M / 30d$3M / 30dwash-filtered genuinewash-filtered genuine: $1.6M / 30d$1.6M / 30dlisted data services (surveyed)listed data services (surveyed): $0.04M / 30d$0.04M / 30d
The headline, on-chain, and wash-filtered tiers come from a16z crypto with Allium and Artemis, March 2026, which flagged roughly 81% of headline volume as gamed. The bottom bar is this census's estimated GMV of the listed data-service catalog at list prices, which is the slice we can independently reconstruct.

Give weight: costly to fake

  • Named institutional commitments carry weight, because a company that joins a standards body puts its lawyers behind the decision.
  • Wash-filtered dollar figures from analysts with no stake in the outcome carry weight.
  • The calls-per-unique-payer ratio carries weight, because real customers call more than once.
  • Endpoint liveness carries weight, because anyone can probe it independently.

Discount: cheap to produce

  • Discount raw transaction counts and "annualized" extrapolations taken off a spike.
  • Discount ecosystem "market cap," which is largely one pre-existing token.
  • Discount unique-payer counts read without the calls-per-payer ratio beside them.
  • Discount anything an incentivized party produced about its own volume.

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.

Method

  • Census: a full offset-paginated walk of 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).
  • The GMV estimate multiplies 30-day calls by the listed price from accepts[].amount, excluding listings priced above $1,000/call (one listing advertises $10B/call). It overstates revenue wherever advertised calls went unsettled.
  • Traffic mix: coarse visitor classes at this seller's hosts (crawler / agent / probe / settled), daily means over July 22 to August 4. No addresses, parameters, or user agents are stored; only the classification is kept (/privacy).
  • Fleet: daily unpaid probe sweep, 500 endpoints per run over a 1,425-endpoint rotation; flags and per-endpoint facts are documented at orcpin.dev/methodology#endpoint_reliability.
  • Coverage caveat: the census covers the CDP facilitator's catalog, which is Base-centric with 175 Solana listings. Rails without open catalogs cannot be censused, and that asymmetry is itself a finding.
  • Live figures on this page come from GET https://orcpin.dev/research.json, which serves catalog size and fleet health only, as ecosystem aggregates.
  • Disclosure: Orcpin sells x402 endpoints, including endpoint-reliability measurements; this page is measurement of a public system by a participant in it.

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.

Calculations

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.

NumberCalculationInputs / result
14,595 listingsThe 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 sellersCount of distinct accepts[0].payTo addresses across all rows.1,094
376,311 paid callsSum of calls over all rows.376,311
73% with ≤1 payerRows with payers ≤ 1, divided by all rows: 10,659 ÷ 14,597.73.0%
Payer histogramRows 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 GMVSum 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 priceMedian of price over the 13,098 rows with a nonzero listed price.$0.01
3,938 listings with ≥2 payersRows with payers ≥ 2; the ratio below is undefined at 0 payers and uninformative at 1.3,498 + 276 + 164
Calls-per-payer bucketsFor 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 listingsRows with payers ≥ 2 and ratio ≥ 3; their calls sum to 282,049.1,008 · 282,049 calls
25 breadth-cluster listingsRows with payers ≥ 50 and ratio ≤ 1.2; their calls sum to 9,509.25 · 9,509 calls
Category chartEach 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 AugustRows 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

References