State of the agent economy
Live measurement of the agent web: supply funnel, live-rate by ecosystem, protocol adoption, revenue concentration, and 30-day growth. Data refreshes every five minutes from the same observability spine that powers every public Agenstry page.
Agenstry’s weekly data show another uptick in discovered agents but virtually no change in actual commerce. We indexed 4,491 agent endpoints (a 6.0% jump from 4,235 a week earlier), of which 276 (6.1%) were live MCP servers【data】. Yet only 21 agents (0.5% of indexed) saw on-chain revenue in the last 30 days (unchanged WoW)【data】. These 21 agents generated $491.02 total (median $6.31), with the top five earning 79.2% of it【data】 and the top ten 95.1% (Gini 0.683, HHI 1495.8). In infrastructure, major players doubled down on enabling agent payments: Stripe’s new Machine Payments Protocol (MPP) – co-developed with fintech Tempo – provides an “internet-native” payment standard for AI agents (stripe.com), and Cloudflare in early July launched an x402-based “Monetization Gateway” to charge for any API or data asset, settling all fees in stablecoins (blog.cloudflare.com). Together these moves (along with the newly announced x402 Foundation consortium) signal growing support for stablecoin rails in the agent economy.
Where the money is flowing
Despite rising discovery, the agent economy’s cash flows remain minuscule and extremely concentrated. In the past 30 days only 21 agents earned at all, splitting $491.02 total – a trivial volume where the median take is just $6.31【data】. The distribution is highly top-heavy (top1 share 21.7%, top5 79.2%, top10 95.1%【data】). These funds flow primarily in stablecoins: for example, Stripe’s Machine Payments Protocol explicitly supports on-chain payments (via stablecoins or fiat) for agent services (stripe.com) (stripe.com), and Cloudflare’s new gateway settles authorizations in USD-pegged tokens (blog.cloudflare.com). Anecdotally, companies are already building on these rails – Stripe notes that services like “Browserbase” let agents spin up browsers and pay per session via MPP (stripe.com). Absent big consumer launches, most investment has been in infrastructure: staffing, wallets, and agent platforms. (For comparison, non-agentic giants continue ramping AI pay capabilities – e.g. Amazon Bedrock’s preview of agentic payments with Coinbase/Stripe in May – but no new fundraising or IPOs tied specifically to agents were reported this week.)
Chart: Daily new agents registered in 30 days (note the single-day spike on July 6).
Spec & protocol
Major standards continue evolving. The Model Context Protocol (MCP) maintainers have published a “2026-07-28” release candidate, introducing a stateless core (breaking existing session-based assumptions), a formal extension framework (Tasks → extension, plus new “MCP Apps”), hardened auth checks and a deprecation policy (blog.modelcontextprotocol.io). This is the largest MCP rewrite to date, and its final spec is on track for July 28 (after a ten-week SDK validation period) (blog.modelcontextprotocol.io). In payments, the Agent-to-Agent standard (x402) is nearing formal adoption: for example, an IETF Internet-Draft co-authored by Stripe/Tempo (“Payment HTTP Authentication Scheme”) was published in March to regularize the agentic 402 challenge/response flow (datatracker.ietf.org). Our agent index shows x402 dominating (525 of 529 cards), with only 3 using the older “l402” fork and 1 using Google’s AP2【data】. Cloudflare has also embedded x402 support directly into its Agents SDK and Workers ecosystem, providing an “x402-proxy” template that automatically returns a 402 challenge on protected endpoints (developers.cloudflare.com). (By contrast, adoption of agent-card signing remains rare: only 31 cards are JWS-signed, ~0.7% of indexed agents【data】.)
Chart: Payment protocols in agent cards (nearly all use x402, as captured in our index【data】).
Notable launches
Cloudflare dominated this week’s announcements. On July 1 it launched a Monetization Gateway – a global edge service that lets any Cloudflare-protected URL (web page, API, even an MCP tool endpoint) require an x402 payment for access (blog.cloudflare.com). All transactions initially settle in USDC (stablecoin) over x402 (blog.cloudflare.com). The Gateway includes a flexible rules API and global Worker templates (e.g. an “x402-proxy” to attach payment checks in front of any endpoint) so that charging agents becomes a configuration task rather than custom dev. Cloudflare says its waitlist is open and aims for sub-second settlement worldwide (blog.cloudflare.com) (blog.cloudflare.com). (Outside of agent-specific projects, broader AI infrastructure news included AWS’s May preview of Bedrock AgentCore payments with Coinbase/Stripe, but no major new launches were reported this week.)
Chart: Drop-off from indexed candidates to earning agents. Only 0.5% of spotted agents show any revenue【data】. (The “Signed” row is agent cards carrying a JWS signature.)
Research
Academic interest in multi-agent AI remains brisk. A new arXiv study found that teams of LLM agents “substantially outperform human teams in creativity” on brainstorming tasks (Cohen’s d≈1.50, comparing 4,541 AI-generated ideas vs 341 human-generated ones) (voiceclone5090.helport.ai). Another group introduced Emergence World, a continuous simulation platform that runs hundreds of LLM-driven agents in a shared virtual world (fed with real weather, news APIs, etc.), to measure long-term dynamics like behavioral drift and governance (huggingface.co). More foundational surveys are appearing too; e.g. one “Hitchhiker’s Guide to Agentic AI” has been posted, aiming to cover the full stack of autonomous agents from theory to deployment. Such work underscores both the promise and complexity of scaling AI agents, but shows that in controlled tests multiple agents can synergize to solve problems beyond a single model’s capability (voiceclone5090.helport.ai).
Regulation
Policy moves in AI and crypto are starting to touch agents. In the EU, on June 29 the Council finalized a new AI regulation that “streamlines and simplifies” existing rules under a single framework (www.consilium.europa.eu) (an “omnibus” package to cut red tape; the impact on agentic systems remains broad and non-specific). Financial regulators in the US have been more pointed: in mid-June FinCEN/OCC proposed treating fiat-backed stablecoin issuers like banks (per the GENIUS Act), requiring them to run full KYC/Customer Identification Programs (www.fincen.gov) (cryptoslate.com). Crypto analysts note this effectively installs identity checks “at the issuer gate” for fiat-to-stablecoin on-ramps, while not extending those requirements into the peer-to-peer transfer layer (cryptoslate.com). No agent-specific law was passed this week, but these developments set the rules of the game for how agents buy assets.
What to watch next week
With the MCP stateless spec set to finalize on July 28, the community will be watching whether major SDKs ship updates in time and whether any interoperability issues arise. The market will also track early usage of Cloudflare’s gateway: as of W29 it’s in private beta/waitlist, so any spikes in x402 transaction volume would be a leading indicator. On the governance side, we expect continued clarity on how regulators apply AML rules to automated agents (e.g. stablecoin KYC); comments on the proposed rules close in late summer. In research, upcoming AI conferences (like NeurIPS workshops) may unveil further multi-agent benchmarks or systems, which could influence the next cycle of the agent ecosystem.
Sources
- Introducing the Machine Payments Protocol
- Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402
- Introducing the Machine Payments Protocol
- The 2026-07-28 MCP Specification Release Candidate | Model Context Protocol Blog
- draft-ryan-httpauth-payment-01 - The "Payment" HTTP Authentication Scheme
- Charge for HTTP content · Cloudflare Agents docs
- Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402
- Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402
- Multi-agent AI systems outperform human teams in creativity · AI-Map
- Paper page - Emergence World: A Platform for Evaluating Long-Horizon Multi-Agent Autonomy
- Inteligência artificial: Conselho dá luz verde final à simplificação e racionalização das regras - Consilium
- FinCEN, Agencies Propose Rule to Implement GENIUS Act Customer Identification Program Requirement | FinCEN.gov
- US starts clock to bring in ID checks for converting dollars to stablecoins but DeFi stays outside the rules
- US starts clock to bring in ID checks for converting dollars to stablecoins but DeFi stays outside the rules
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.
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.
A2A vs MCP vs paid_api
x402 / AP2 / Stripe MPP / L402
New agents per week, by payment protocol
A few agents earn most of the money.
Across the 21 agents observed to have on-chain revenue in the last 30 days, the distribution is heavily power-law. Gini and HHI quantify how concentrated the spend is at the top.
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.
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.
Agenstry Research. "State of the Agent Economy." Accessed 2026-07-13. https://agenstry.com/reports/state-of-agent-economy
@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-07-13},
year = {2026}
}
<iframe src="https://agenstry.com/reports/state-of-agent-economy" width="100%" height="900" frameborder="0"></iframe>
All revenue 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.
Not included: revenue agents earn 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 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. Revenue is derived from on-chain x402 USDC 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.
Weekly State of the Agent Economy
Top earners · biggest 7-day movers · payment-rail adoption · methodology, straight from our index. Free, Mondays.