← Orcpin · Orcpin Research · Monthly Snapshot
When an AI agent visits a paid service, it does one of three things. Some visitors are watchers: crawlers, indexers, and security scanners that have no way to pay. Some are evaluators: agents that ask what the service costs and then walk away. A few are purchasers: wallets that actually pay. The middle group matters more than it looks. An evaluator may well have money and still decline, because its instructions don't allow a purchase at that price or for that purpose. You can only tell a funded wallet from an empty one at the moment it pays, so the three groups are defined by what they do, not what they hold — and a low rate of sales is a mix of agents that can't pay and agents that chose not to. Most published numbers lump all three together. This report measures the split. It reads every listing in the largest public catalog of pay-per-use services for agents, checks daily whether those services still answer, records the mix of visitors at Orcpin's own services, and maps the payment networks the wallets use. This is the third full read of the catalog and the second published edition, so for the first time the report can show movement rather than a still frame. Everything here is a count or a cited fact; nothing is advice. Sources are listed at the end.
The month in four numbers
The catalog stopped shrinking. After falling from 25,529 listings in July to 14,595 in August, it grew a little, to 14,913 in September, and the number of sellers rose with it, from 1,094 to 1,127. On the supply side, things are steady.
Purchases went the other way. Paid requests across the whole catalog fell from 376,311 to 281,361 over comparable 30-day windows, a drop of 25%, and our estimate of total sales at the listed prices fell from about $40K to $32K. More listings, more sellers, a quarter fewer purchases.
That drop is not spread across the catalog. It is one category. Paid requests to web-search and scraped-data services fell from 208,728 to 80,700 — a loss of 128,028 requests, which is more than the catalog's entire net decline. Set web search aside, and the rest of the catalog grew, from 167,583 paid requests to 200,661, up 20%. One category was carrying the measured economy in August, it shrank by 61% in a month, and that shrinkage is the whole story behind the headline number. Anyone quoting a catalog-wide total for this market without that breakdown will read a downturn where the measured fact is much narrower.
Three reads of the same catalog
| What we counted | July 16 | August 5 | September 1 |
|---|---|---|---|
| Services listed | 25,529 | 14,595 | 14,913 |
| Distinct sellers | 1,117 | 1,094 | 1,127 |
| Paid requests in the prior 30 days | 313,580 | 376,311 | 281,361 |
| Paid requests, web search set aside | — | 167,583 | 200,661 |
| Listings with no purchases at all | 42.7% | 0.8% | 0.6% |
| Listings with one paying wallet or none | — | 73.0% | 73.8% |
| Estimated 30-day sales at listed prices | — | $39,982 | $32,208 |
| Typical listed price per request | — | $0.01 | $0.01 |
August's reading was that the catalog got smaller and cleaner while activity grew, which looked like dead listings being pruned rather than sellers leaving. September revises that: the pruning stopped and the catalog resumed slow growth, but the rise in activity did not hold. Taken together, the two months suggest the July-to-August jump in purchases was concentrated enough in one category to reverse within a month — a caution against reading any single month's direction as a trend. Only repeated monthly reads can show this. One snapshot cannot, and two are barely enough.
Agents no longer pay through one system. By mid-2026 every major payment company has launched or announced a way for agents to pay. The systems differ in who holds the money and in what an outsider can see. Each status below is a dated public announcement, not a judgment of how mature the system is.
| System | Who runs it | How money moves | Status (with source) | Can an outsider measure it? |
|---|---|---|---|---|
| Link agent wallet, Shared Payment Tokens, Issuing for agents | Stripe | card payments; single-use virtual cards with limits | announced at Stripe Sessions 2026 (Stripe blog, docs) | no public usage data per service |
| Machine Payments Protocol on Tempo | Stripe | Tempo, a blockchain Stripe incubated; batches tiny payments | live March 2026 (Forbes, Mar 2026) | the blockchain is public, and the mpp.dev directory lists 142 services with prices but publishes no usage per service. Corrected September 8: the September 1 edition said there was no directory. |
| Visa Intelligent Commerce / Visa Payment Passkeys | Visa | card payments with a stand-in credential instead of the real card number | real purchases made by agents at merchants in Europe, with 30+ participating banks, July 2026 (Visa press; Payment Expert, Jul 2, 2026) | no usage data per service |
| Agent Pay + Verifiable Intent | Mastercard | card payments with agent-specific credentials; the up-to-$1.8B purchase of BVNK adds digital-dollar settlement, completed Aug 3, 2026 (Mastercard press) | rolling out through 2026 | no |
| System | Who runs it | How money moves | Status (with source) | Can an outsider measure it? |
|---|---|---|---|---|
| x402 | Coinbase + Cloudflare; the x402 Foundation (Linux Foundation) | USDC, a dollar-pegged digital token, on the Base and Solana blockchains; the service quotes a price in the web response itself | the Foundation launched July 14–15, 2026 with Visa, Mastercard, Amex, Stripe, Adyen, Fiserv, Shopify, Google, AWS, Cloudflare, Circle, and Ripple as premier members (Linux Foundation press) | yes — the only system with an open catalog of services and payments recorded on a public blockchain |
| Bedrock AgentCore Payments | AWS + Coinbase | x402 underneath | announced 2026 (Coinbase blog); CloudFront support for x402 is generally available | through x402's public surfaces |
| Pay-per-crawl + x402 gateway | Cloudflare | charges for web requests at Cloudflare's edge, using x402 | applications for the gateway opened July 1, 2026 | totals only |
| L402 | Lightning community | Bitcoin's Lightning network, with the price quoted in the web response | a published spec with a few small deployments | partly — Lightning hides most activity by design |
| System | Who runs it | How money moves | Status (with source) | Can an outsider measure it? |
|---|---|---|---|---|
| KYAPay / Know-Your-Agent credentials | Skyfire (with Experian's framework; Fastly verifies at the edge) | works on top of any network; a signed identity travels with each request | draft internet standard, March 2026 (draft-skyfire-kyapayprofile) | the credential can be checked; how many are used is not published |
| AP2 mandates / Verifiable Intent | Google / Mastercard | works on top: a signed record of what the person authorized | specs published; adoption in progress | no |
| Endpoint reliability facts | Orcpin (the publisher of this report) | works on top of x402: free checks that a service still answers, plus paid checks that it delivers, sold per request | live since June 2026 (published method) | yes — the measured facts are summarized in this report |
| System | Who runs it | How money moves | Status (with source) | Can an outsider measure it? |
|---|---|---|---|---|
| Agentic Commerce Protocol (ACP) | OpenAI + Stripe | card payments; originally checkout inside the chat window | the in-chat Instant Checkout feature was withdrawn in March 2026 after about six months, over reported conversion results; the protocol itself is still published and was extended toward product discovery (Forbes, Mar 10, 2026) | no |
| UCP / Agentic Checkout | checkout inside Google's platform | Q2 2026 (Q2 2026 10-platform matrix) | no | |
| Shopify Agents · Amazon Buy for Me · Klarna Agent Mode | the respective platforms | closed; only approved merchants | Q2 2026 (same matrix) | no |
Two things follow from that last column. First, x402 is the only system whose list of services and whose payments are open for anyone to measure, which is why the rest of this report can exist at all; every other system publishes announcements, not populations. Second, every one of them has separately arrived at this report's exact question — how do you tell an agent that can spend money from a bot that only looks? The card networks answer it with identity credentials and passkey approvals; x402 answers it with per-service counts of paying wallets. The mechanisms differ; the dividing line is the same.
The ACP row deserves a closer look. The most-publicized agent checkout of 2025 was withdrawn in March 2026 for lack of conversions while its underlying standard stayed in place. That is the same gap this report measures on the x402 side, where listings and standards pile up faster than purchases.
Orcpin sells pay-per-request services on x402, which makes it a measuring point: every visitor is sorted into a coarse class and nothing else is kept — no addresses, no request details, no identities (see /privacy). The chart shows each group's share of Orcpin's daily visits, for the 13 days ending August 31, next to the same figure from the August edition. Shares rather than counts are deliberate: the shape of the funnel is the finding, and one seller's sales volume is private.
More than 999 of every 1,000 daily visits still involve no money. The watchers still include hundreds of daily attempts to fetch /.env and similar secret files, which is background internet noise every public server sees and has nothing to do with agents at all. The change this month is in the evaluators: their share rose from 26% to 34%. That is not because more agents asked for prices — those requests were roughly flat at about 1,650 a day — but because automated reads of the free catalog pages dropped sharply while crawler traffic stayed level. The mix changed; the actual rate of price-checking did not. Either way, money only enters the picture at the moment of payment, and paying remains by far the rarest thing on the chart. One seller is one sample; the survey below shows the same shape across the whole catalog.
On September 1 we read every listing in the CDP Bazaar, the public catalog of x402 services, along with Coinbase's own figures for how much each was used in the prior 30 days. This is the whole listed population, not a sample. The three-month table above holds the headline totals; the charts below show how those totals are distributed, and how that distribution moved since August.
This is the month's second breakdown, and it points the same way as the first. The number of repeat-use listings barely moved (1,008 to 972), but the requests they carried fell 41%, from 282,049 to 165,859 — so repeat business fell faster than the catalog as a whole. Meanwhile the one-time-use listings grew their requests 55%, from 9,509 to 14,745, on essentially the same 25 or so listings. Repeat use went from 75% of all paid requests to 59% in one month.
The one-time pattern matters because the catalog ranks services by how many different wallets have paid them. That rewards being touched once by many wallets over being used repeatedly by a few — an incentive the academic literature has described in general form (TraceRank, arXiv 2510.27554). We publish the distribution and the definitions. Whenever you see a count of paying wallets, here or anywhere, the requests-per-wallet figure belongs beside it.
The catalog keeps confirming the same picture of demand, and this month's movement sharpens it rather than overturning it: what sells is what an agent cannot get without paying someone. That means web and social data behind paywalls, lookups of people and companies, compute and execution, and real-world goods. What does not sell is data an agent can fetch for free from any public blockchain node. The blockchain-data category now holds 5,568 listings, more than a third of the catalog, and receives 21% of paid requests — a bigger share than in August, but only because the total shrank; its own request count rose modestly, from 56,350 to 60,024. Supply is still concentrated exactly where demand is thinnest.
Two category movements are worth stating plainly because they cut against the headline. Prices and trading rose from 27,593 to 37,722 requests on a growing set of listings, and AI model calls rose from 14,336 to 17,532. The keyword rules also moved a large block: the people-and-company-lookup category fell from 1,186 listings to 519, which reflects a change in how listings describe themselves as much as a change in what exists. Read category listing counts with that caveat.
Beneath the usage layer is a simpler question: does the service still answer at all? Some listed services will never see a purchase because nothing is there any more. Every day we send free test requests to roughly 500 listed services — asking for the price is free — rotating through a growing list that stood at 2,167 services on September 1, up from 1,425 in August:
The one figure in this report that is a dollar total — about $32K of sales across the listed catalog in 30 days, down from about $40K in August — is the smallest of four very different ways of counting the same month. The three larger tiers (as reported on dashboards, verifiable on the public ledger, and after fake volume is removed) come from an independent March 2026 analysis and do not change from edition to edition, so they are not reprinted here. The standing reading guide — the four tiers side by side, what to take seriously, and what to take lightly — lives on the methodology page. Read this report's total against that scale, not on its own.
api.cdp.coinbase.com/platform/v2/x402/discovery/resources (100 listings per page, 150 pages) on September 1, 2026, and removed duplicate URLs. Per-listing 30-day usage figures are Coinbase's own quality fields, copied rather than audited. The August 5 read used the identical recipe (146 pages), as did the internal July 16 read (256 pages).accepts[].amount, leaving out listings priced above $1,000 per request. It overstates real revenue wherever a request was made but never paid for.GET https://orcpin.dev/research.json publishes this edition's catalog figures alongside the current state of the daily check; that second part moves every day and will therefore drift from the September 1 run pinned here.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 catalog rows with one of the formulas below. The data file keeps one row per listing, carrying Coinbase's own 30-day figures: payers (quality.l30DaysUniquePayers, distinct paying wallets), calls (quality.l30DaysTotalCalls, paid requests), and the listed price (accepts[0].amount, in millionths of a dollar, so USD = amount ÷ 1,000,000). The machine-readable summary with these same buckets is generated by npm run census.
| Number | How it is calculated | Inputs / result |
|---|---|---|
| 14,913 listings | The catalog's own pagination.total at read time. Removing duplicate URLs leaves the same 14,913 rows this month (August had two duplicate URLs); every distribution figure uses the de-duplicated rows. | 14,913 reported · 14,913 unique |
| 1,127 sellers | Count of distinct accepts[0].payTo addresses across all rows. | 1,127 |
| 281,361 paid requests | Sum of calls over all rows. | 281,361 |
| Down 25% from August | (281,361 − 376,311) ÷ 376,311, against the August 5 read. | −94,950 · −25.2% |
| Up 20% with web search set aside | Total paid requests minus the search category's, per edition: September 281,361 − 80,700; August 376,311 − 208,728. | 167,583 → 200,661 · +19.7% |
| 74% with one paying wallet or none | Rows with payers ≤ 1, divided by all rows: 11,002 ÷ 14,913. | 73.8% |
| Paying-wallet chart | Rows bucketed by payers: exactly 0, exactly 1, 2–5, 6–20, 21 and over. Buckets sum to 14,913. August, same buckets: 121 · 10,538 · 3,498 · 276 · 164 (sum 14,597). | 93 · 10,909 · 3,397 · 400 · 114 |
| ≈$32K in sales | Sum of calls × price over rows with a listed price of $1,000 per request or less (the cap removes placeholder prices). | $32,208 over 14,579 rows |
| $0.01 typical price | Median of price over the 14,672 rows with a nonzero listed price. | $0.01 |
| 3,911 listings with 2+ paying wallets | Rows with payers ≥ 2; the ratio below is undefined at 0 wallets and uninformative at 1. | 3,397 + 400 + 114 |
| Requests-per-wallet chart | For each of those rows, ratio = calls ÷ payers, bucketed at ≤1.2, ≤3, ≤20, ≤100, and over 100. August, same buckets: 1,410 · 1,623 · 722 · 155 · 28 (sum 3,938). | 1,138 · 1,904 · 699 · 131 · 39 |
| 972 repeat-use listings | Rows with payers ≥ 2 and ratio ≥ 3; their requests sum to 165,859, or 58.9% of all paid requests (August: 1,008 listings, 282,049 requests, 75.0%). | 972 · 165,859 requests |
| 26 one-time-use listings | Rows with payers ≥ 50 and ratio ≤ 1.2; their requests sum to 14,745 (August: 25 listings, 9,509 requests). | 26 · 14,745 requests |
| Category chart | Each row takes the first matching category from an ordered keyword list applied to its name, description, tags, and URL (the ordered list is in scripts/census.ts); calls are then summed per category, for each edition. | 12 categories · 2 editions |
| Listings with no purchases, three editions | Rows with calls = 0 divided by all rows, per edition: July 10,890 ÷ 25,529; August 121 ÷ 14,597; September 92 ÷ 14,913. (Rows with zero recorded requests; the 93 in the paying-wallet chart is the separate count of rows with zero paying wallets.) | 42.7% → 0.8% → 0.6% |
| Visitor shares (66% · 34% · <0.1%) | Visitor-class counters summed over August 19 to August 31 and divided by 13, then expressed as shares of all daily visits. Watchers combine crawler-class visits (2,826/day, including unclassified) and automated catalog reads (427/day); evaluators are free price checks on paid services (1,647/day); purchasers are paid requests, whose share is below one visit in a thousand. August, same method over July 22 to August 4: 74% · 26% · <0.1% of ≈6,870 daily visits (crawlers 2,968/day, catalog reads 2,127/day, price checks 1,774/day). Paid-request counts are not disclosed. | shares of ≈4,900 daily visits |
| Daily-check chart (231 · 162 · 101) | From the September 1 check of 494 services: 231 answered correctly and 162 had fewer than five samples (too few to say); the remaining 101 = 494 − 231 − 162 carried a failure or overdue state. August 4, for comparison: 213 · 259 · 28 of 500. | 231 + 162 + 101 = 494 |
api.cdp.coinbase.com/platform/v2/x402/discovery/resources. Full reads on July 16, August 5, and September 1, 2026; per-listing 30-day usage figures are Coinbase's own quality fields.https://orcpin.dev/research.json.