Skip to content
Report · auto-updating

State of the agent economy

Live measurement of the agent web: supply funnel, live-rate by ecosystem, protocol adoption, inflow concentration, and 30-day growth. Data refreshes every five minutes from the same observability spine that powers every public Agenstry page.

As of 2026-08-21 01:36:04 UTC methodology JSON CSV cite this archive
Weekly briefing · 2026-W21 archived view
May 18, 2026

Early metrics show the agent economy is still nascent. Our probes found 2,607 AI agents indexed, but only 101 (~3.9%) were live (introspectable) and just 21 (0.8%) earned any on-chain revenue in 30 days. Total observed 30-day agent revenue was only $495.65, with a median of $6.31 per earning agent (95th percentile $98.75), and the top 10 agents capturing 95.4% of the volume (Gini ≈ 0.675). In short, the vast majority of agents do almost no business. Yet protocol governance is moving: Google has donated its Agent Payments Protocol (AP2) to the FIDO Alliance and released AP2 v0.2 with new autonomous (“human-not-present”) payment features (blog.google). Likewise, the Linux Foundation has launched the x402 Foundation, taking over the open x402 rail originally built by Coinbase/Stripe/Cloudflare (www.linuxfoundation.org). Both moves were supported by industry leaders (e.g. AWS, Google, Visa, Mastercard) aiming to standardize agent commerce.

Where the money is flowing

New payment rails and partnerships are forming even as agent revenues stay tiny. Crypto-native x402 saw rapid use: reports claim ~3.3 million transactions in 30 days on x402 (averaging just $0.46 each) (www.kucoin.com). But big payments players are also entering. For example, Stripe partnered with the Tempo blockchain to introduce its Machine Payments Protocol (MPP) – an open, stablecoin/fiat payment standard – on Tempo’s mainnet (www.theblock.co) (www.kucoin.com). (Tempo’s March 2026 launch bundled MPP and a directory of merchants.) Visa and Mastercard are likewise building agent rails: they co-developed Stripe’s AP2 and donated its new “Verifiable Intent” log standard to FIDO (blog.google), and are active in emerging APIs. In parallel, the Model Context Protocol (MCP) is gaining traction as the standard agent-to-API interface – major issuers (Stripe, Visa, Mastercard) have signaled MCP integration work (www.kucoin.com).

The chart below shows which discovery sources yielded the most live agents. Traditional registries and search crawls still dominate: our registry list found 64 live agents, while “recrawl_hot” (popular agent sites) found 50, and the new A2A-specific registry had 39 live entries. Many agents are being found via GitHub (32 live) and an MCP-centric registry (21 live). These panels illustrate the early ecosystem pipelines for agent discovery.

Live Agents by Discovery Sourceregistry64recrawl_hot50a2aregistry39github_code32mcp_registry21

In terms of payment methods, the vast majority of indexed agents are not yet on any rail. Only 784 of 2,607 agents have an x402 setup (and only 2 have L402), leaving ~1,821 with no payment protocol. The donut chart below highlights the imbalance: roughly 30% of agents have x402 enabled; nearly all others remain unconnected to an on-chain payment scheme (and a negligible slice use L402). This underlines how early most agents are in adding commerce features.

Agent Payment Protocol Usage2.6Knone1.8K · 69.9%x402784 · 30.1%l4022.00 · 0.1%

Notably, although most agentatives make no revenue, crowds of conventionally real companies are investing in agentic commerce infrastructure. Startups like Skyfire and Halliday (per industry tracking) have raised on the order of $10–15 million to build x402-based payment and escrow services. On the consumer side, Amazon this week rolled out an AI shopping assistant (integrating the “Rufus” agent into Alexa) that can autonomously shop for users (www.axios.com) – showing that household-name platforms see value in letting agents transact. How and when such bots will plug into standards like AP2 or x402 remains to be seen.

Spec & protocol

Standards development accelerated this month. In payment protocols, Google’s gift of AP2 to the FIDO Alliance (announced April 29) has been followed by release of AP2 v0.2 (blog.google). This update adds support for “human-not-present” automated payments, letting pre-authorized agents execute purchases without interrupting users. Google also highlighted a new AP2-compatible “Verifiable Intent” log (co-built with Mastercard) to record user-approved actions (blog.google). The aim is to anchor agent transactions in cryptographically verifiable user consent; these specs now fall under FIDO’s open-standards process.

Meanwhile, x402 – the HTTP-402 agentic payments spec – has been submitted to the Linux Foundation. The new x402 Foundation (announced April 2) will steward the protocol originally developed by Coinbase, Stripe and Cloudflare (www.linuxfoundation.org). The press release lists dozens of member companies (Amazon, Adyen, AWS, Google, Mastercard, Microsoft, Solana, Visa, etc.) investing into x402 governance (www.linuxfoundation.org). In short, two main rails (AP2 and x402) are now in neutral, industry-led groups.

On the communication side, enterprise integrations are maturing. ServiceNow and Google Cloud announced a joint solution (Apr 22) that uses the A2A protocol and MCP to let agents across enterprise systems exchange tasks securely (www.streetinsider.com). This is one of the first public demonstrations of an A2A/A2UI/MCP “agent chain” at scale. The latest MCP roadmap (Mar 2026) likewise emphasizes transport scalability and enterprise readiness (blog.modelcontextprotocol.io). In practice, however, implementation is still sparse: for example, none of the agent cards we’ve seen are yet cryptographically signed (0% Signed in our data), meaning integrity checks remain a forthcoming feature.

Research & analysis

Academia and industry labs are analyzing the emerging agent economy. A major recent survey (Zhang et al., Apr 2026) systematized blockchain-based A2A payment designs like x402, identifying open challenges around intent binding and multi-party accountability (arxiv.org). Other new papers take constructive approaches: “ClawCoin” proposes a compute-indexed cryptocurrency as a shared unit for agent workflows (arxiv.org), addressing the gap between fiat rails and compute costs. Simulations by Liu et al. (“When Agent Markets Arrive”, Apr 2026) show that agent-to-agent marketplaces can triple wealth compared to standalone agents, but also that market design (e.g. visibility of identities, selection rules) crucially impacts outcomes (arxiv.org). And Uddin et al. (APEX, Apr 2026) show how HTTP-402-style micropayment gating can be adapted to fiat systems (like India’s UPI) with built-in spending policies and security (arxiv.org) – a blueprint for real-world agent payments without crypto. In short, research is actively exploring both theoretical and practical facets of agent commerce.

What to watch next week

The key question is who will be first to connect these pieces in practice. Keep an eye on any announcements around agent payment pilots or protocol testbeds. For example, Amazon’s new “Alexa for Shopping” rollout on May 13 (www.axios.com) signals that consumer-facing agents are arriving; it will be telling if Amazon or other big platforms soon adopt open rails (AP2, x402 or MCP) to handle backend transactions. In the open-source community, look for progress in agent card signing or AP2/FIDO working groups – these will be the milestones that turn today’s experimental agents into production commerce participants.

Sources

  1. Google donates Agent Payments Protocol to FIDO Alliance
  2. Linux Foundation is Launching the x402 Foundation and Welcoming the Contribution of the x402 Protocol
  3. IOSG: AI Agent Payment Infrastructure Enters the Race for the Machine Economy’s Stripe | KuCoin
  4. Tempo Mainnet goes live with Machine Payments Protocol for agents | The Block
  5. IOSG: AI Agent Payment Infrastructure Enters the Race for the Machine Economy’s Stripe | KuCoin
  6. Google donates Agent Payments Protocol to FIDO Alliance
  7. IOSG: AI Agent Payment Infrastructure Enters the Race for the Machine Economy’s Stripe | KuCoin
  8. Amazon pushes Alexa+ deeper into AI-powered shopping
  9. Linux Foundation is Launching the x402 Foundation and Welcoming the Contribution of the x402 Protocol
  10. ServiceNow and Google Cloud unite AI agents for autonomous enterprise operations
  11. The 2026 MCP Roadmap | Model Context Protocol Blog
  12. SoK: Blockchain Agent-to-Agent Payments
  13. ClawCoin: An Agentic AI-Native Cryptocurrency for Decentralized Agent Economies
  14. When Agent Markets Arrive
  15. APEX: Agent Payment Execution with Policy for Autonomous Agent API Access
1 · Supply funnel

Most of the agent economy is indexed, not yet operational.

Counting agents conflates supply with operation. Below is the corpus broken into five stages: what fraction of indexed agents pass each gate. The decay curve is the honest read on how mature the agent web is at any given moment.

Stage Count % of indexed Definition
Indexed 6,841
100.0%
Every candidate we have seen across every source.
Valid card 5,308
77.6%
Returned a parseable A2A/MCP card on probe.
Live 507
7.4%
Live JSON-RPC / introspectable MCP.
Signed 64
0.9%
Card published with a JWS signature.
Earning (30d) 1,903
27.8%
Agents where we observed inbound USDC/EURC settlement to their declared x402 payTo wallet. Measured over the wallets scanned so far (1404 of 1477 with a wallet) — not an ecosystem-wide total.
2 · Live-rate by ecosystem

Which source registries actually ship live agents.

Each row shows one source registry (Anthropic's MCP directory, Smithery, Glama, Postman, GitHub well-knowns, Wayback CDX scans) alongside how many of the agents it lists actually respond live on probe. The gap between seen-count and live-count is the source's effective freshness.

Source Seen Live Live rate
recrawl_hot 3,114 374 12.0%
agentic_market 2,753 66 2.4%
recrawl_warm 2,445 169 6.9%
mcp_registry 1,644 221 13.4%
cdp_discovery 1,286 36 2.8%
manifests 873 90 10.3%
github_code 760 66 8.7%
lists 481 19 4.0%
x402_list 368 16 4.3%
registry 337 185 54.9%
recrawl_cold 290 2 0.7%
n8n_workflows 194 0 0.0%
github_topics 149 4 2.7%
a2aregistry 114 87 76.3%
a2a_registry_org 112 40 35.7%
3a · By protocol kind

A2A vs MCP vs paid_api

paid_api
3,427
a2a_agent
1,880
a2a
4
3b · By observed payment-protocol label

Index composition, not global market share. x402 has multiple dedicated catalogs and a live HTTP probe; AP2, L402 and Stripe ACP are predominantly visible only when cards declare them.

x402 / AP2 / Stripe MPP / L402

x402
3,450
mpp
83
a2a_x402
24
ap2
19
l402
3
stripe_spt
1
3b · Evidence grade

How we know they take payment

275 of 3,580 payment-labelled agents (7.7%) proved it themselves — their own endpoint answered an unpaid request with an HTTP 402 challenge, or the host serves a /.well-known/x402 manifest. The rest is declared in a static agent card or described by a third-party catalog.

Facilitator feed
2,010
Catalog listing
962
Agent card
226
Live 402 challenge
196
Official protocol directory
82
/.well-known/x402
75
Not re-probed yet
25
mpp_challenge
4
3c · Indexed protocol labels over time · last 12 weeks

Newly indexed agents per week, by payment label

Changes reflect both ecosystem activity and changes in crawler source coverage.

2026-W22 · a2a_x402: 2 2026-W22 · ap2: 1 2026-W22 · x402: 1 22 2026-W23 · x402: 7 2026-W24 · ap2: 1 2026-W24 · l402: 1 2026-W24 · x402: 7 24 2026-W25 · a2a_x402: 1 2026-W25 · ap2: 2 2026-W25 · x402: 17 2026-W26 · a2a_x402: 1 2026-W26 · ap2: 1 2026-W26 · x402: 5 26 2026-W27 · a2a_x402: 4 2026-W27 · x402: 9 2026-W28 · a2a_x402: 2 2026-W28 · x402: 1144 28 2026-W29 · a2a_x402: 1 2026-W29 · ap2: 1 2026-W29 · mpp: 1 2026-W29 · x402: 245 2026-W30 · a2a_x402: 2 2026-W30 · x402: 302 30 2026-W31 · a2a_x402: 1 2026-W31 · ap2: 1 2026-W31 · mpp: 81 2026-W31 · x402: 260 2026-W32 · a2a_x402: 3 2026-W32 · ap2: 2 2026-W32 · x402: 224 32 2026-W33 · a2a_x402: 4 2026-W33 · ap2: 3 2026-W33 · x402: 223 2026-W34 · x402: 138 34
a2a_x402 ap2 l402 mpp x402
4 · Inflow concentration · 30d

A few settlement wallets receive most of the money.

Across 926 earning wallets backing 1,903 linked services, the distribution is heavily power-law. Wallet-level Gini and HHI avoid multiplying transfers when several catalog entries share one recipient.

Observed inflow · 30d
$256062.47
Recipient wallets
926
Median · wallet
$0.266
p95 · wallet
$45.81
Top 1 share
69.8%
Top 5 share
94.1%
Gini
0.994
extreme inequality
HHI
5058
highly concentrated
5 · 30-day growth

New agents arriving daily, by first-seen.

Daily count of agents we discovered for the first time. Sourced from every registry + open-web crawl we run.

2026-07-23 peak 331/day 2026-08-21
New agents · 30d
+1,690
Earning agents · 30d
1,913
observed in the snapshot table
6 · Demand gaps

What the market asked for and didn't get.

Every section above measures the supply we indexed. This one measures demand we couldn't serve: clustered search intents — from browsers, AI assistants and agents calling our A2A and MCP endpoints — where the index returned nothing or almost nothing. Aggregate only, and shown only for intents searched by enough distinct sources to be a market signal rather than one person's session.

Intent Demand Unmet Trend
audio transcription very active 56% rising

Full list + method: what the agent economy is missing. Building one of these? Add pay-per-call payments to your API →

Cite this report

Public domain numbers (CC BY 4.0). Pick the format that fits. The page auto-updates so the URL is the canonical pointer; the date stamps the snapshot you cited.

Plain text
Agenstry Research. "State of the Agent Economy." Accessed 2026-08-21. https://agenstry.com/reports/state-of-agent-economy
BibTeX
@misc{ '{' }}agenstry_state_of_agent_economy,
  title  = {State of the Agent Economy},
  author = {Agenstry Research},
  url    = {https://agenstry.com/reports/state-of-agent-economy},
  note   = {Accessed 2026-08-21},
  year   = {2026}
}
Embed (iframe)
<iframe src="https://agenstry.com/reports/state-of-agent-economy" width="100%" height="900" frameborder="0"></iframe>
Scope What this report measures, and what it doesn't

All inflow numbers are on-chain: direct eth_getLogs scans of USDC Transfer events (plus EURC on Base + Ethereum) into each indexed agent's payment_wallet across Base, Ethereum, Polygon, Arbitrum, Optimism (EVM via eth_getLogs) and Solana (SPL via getSignaturesForAddress). Reproducible from public RPC; not based on self-reporting. We report money arriving at those wallets — we do not verify that each transfer was an arm's-length sale, and we do not net out transfers an operator sends itself. See the measurement boundary.

Not included: money agents take via Stripe (per-agent Stripe accounts are private), Patreon / Sponsors, direct credit cards, PayPal, or any off-chain rail. Agenstry's own platform-skill revenue (compose / agent_stats / etc.) is also excluded: it lives in a separate accounting table that never feeds public totals. This is "the observable on-chain slice of the agent economy", not "all agent revenue ever". Off-chain rails will appear here only when the operator opts in to a future verified-reporting feed.

Methodology

Every figure on this page is computed from the same observability tables that power the rest of the Agenstry surface, with no synthetic data and no manual curation. The crawl ingests eight federated sources plus open-web well-known probes. Agents are scored against a 9-criterion conformance methodology. Observed inflow is derived from on-chain USDC/EURC transfer scans across six chains: Base, Ethereum, Polygon, Arbitrum, Optimism, and Solana; AP2 / Stripe MPP / L402 receipts are detected on agent cards but indexed only when the rail is publicly verifiable. The full crawl + scoring pipeline is open behind the federation feed. If our numbers disagree with yours, one of us has a bug, and we would like to know.