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.
Agenstry’s September 14 snapshot shows discovery expanding faster than operational quality: 9,271 candidates are indexed, up +1,230.00 (+15.3%) from 2026-W37, while live endpoints rose +42.00 (+5.7%) to 776. Revenue remains real but unusually concentrated: observed 30-day gross settlement is 216639.16, yet the top agent captures 82.5 percent and the HHI increased from 5,487.40 to 6,840.90 week on week.
Discovery is broadening faster than execution
The funnel remains the central operational fact. Of 9,271 indexed candidates, 6,954 return a valid card, 776 are live, and 109 are signed. That leaves live, cryptographically signed service discovery as a narrow layer beneath a much larger corpus of declared capabilities. The strongest observed live rates sit in the a2aregistry source at 82.0 percent and registry at 62.5 percent, whereas high-volume discovery channels are materially less dependable: recrawl_hot is 14.8 percent live and agentic_market is 2.5 percent live.
The intake pace accelerated. new_agents_30d rose from 1,883.00 to 2,787.00, a delta of +904.00 (+48.0%). The two conspicuous intake days were September 8, with 295, and September 9, with 652. These spikes should be treated as discovery events rather than evidence of durable service supply until the associated cards clear live probing and payment-challenge verification.
The chart highlights the difference between observable economic activity and endpoint operability. 2,502 agents are classified as earning over 30 days, measured across 1,795 of 1,958 wallet-bearing agents that were scannable; this is expressly a wallet-observation measure, not an ecosystem-wide estimate.
Where the money is flowing
Observed 30-day gross settlement is 216639.16 across 2,502 earning agents and 1,276 earning wallets. The median agent records 0.255, while the p95_usd_30d is 44.6397. That gap is reinforced by a 0.994 Gini coefficient, 82.5 percent top-one share, 93.5 percent top-five share and 95.1 percent top-ten share.
The relevant week-on-week movement is not broader monetisation but greater concentration: total_earning increased only +16.00 (+0.6%), while HHI rose +1,353.50 (+24.7%). For CIOs and investors, the implication is that demand exists, but it is being captured by an exceptionally small set of endpoints. The immediate diligence question is therefore less whether agents can charge and more whether leading earners have defensible distribution, reliable fulfillment and verifiable service quality.
Spec and payment rails
The payment layer remains overwhelmingly x402-labelled: 4,567 entries are associated with x402, compared with 90 for MPP, 42 for a2a_x402, 23 for AP2, 4 for L402 and 1 for stripe_spt. But protocol declarations should not be confused with runtime proof. Of 4,727 labelled entries, just 343 are self-declared live, or 7.3 percent, based on an endpoint returning an unpaid HTTP 402 challenge or serving a /.well-known/x402 manifest.
The 2026-W38 cohort currently contains 21 payment-protocol records, all x402; because the snapshot is timestamped September 14 and 2026-W38 begins September 14, it is not comparable with the completed 345-record 2026-W37 cohort. At the implementation layer, the x402 project’s early-September work focused on operational plumbing rather than a new economic primitive: batch-settlement minimum-deposit hints, settlement handling and facilitator-client timeout changes were among the merged updates. x402 repository activity (github.com)
MCP’s larger transition remains consequential for the supply side. The current 2026-07-28 specification made the protocol stateless, added an extensions framework and hardened authorization; its roadmap now puts Tasks, Apps, discovery and enterprise readiness at the centre of subsequent work. MCP release notes MCP roadmap (blog.modelcontextprotocol.io) This week’s MCP governance work also includes proposed documentation for Skills-extension support tracking and a client support matrix for Tasks. MCP pull requests (github.com)
Enterprise controls are becoming part of the product
Commercial announcements this week were concentrated in merchant connectivity and control planes, rather than open agent marketplaces. IXOPAY launched an Agentic Suite combining a payment agent, transaction-context tokens and an MCP server for governed access to payment and tokenisation capabilities. IXOPAY announcement (ixopay.com) Mastercard also introduced merchant-facing shopping-agent capabilities and Agent Connect access through its Agent Suite for Merchants. Mastercard announcement (mastercard.com)
Security is moving from guidance toward runtime enforcement. OWASP published its Agent Control Standard on September 1, framing portable middleware hooks and declarative, runtime-enforced policies as the basis for agent inspection and control. OWASP Agent Control Standard (genai.owasp.org) The direction is consistent with recent research proposing pre-admission vetting and task-aware runtime authorization for MCP-style tools. ToolGuardian paper (arxiv.org)
Regulation
The regulatory benchmark is now concrete in Europe: Article 50 transparency obligations under the EU AI Act have applied since 2 August 2026, including requirements tied to informing people when they interact with AI systems; the Commission notes a limited transition for certain pre-existing systems’ AI-content marking obligations until 2 December 2026. European Commission guidance (digital-strategy.ec.europa.eu) Singapore’s January framework remains a useful operational template, emphasizing bounded powers, meaningful human accountability, lifecycle controls and user transparency for agent deployments. IMDA framework announcement (imda.gov.sg)
What to watch next week
The specific item to track is whether the September 14–20 cohort develops beyond its current 21 x402-labelled records into runtime-verifiable payment endpoints. A sustained rise in self-declared live payment challenges—not static catalog entries—would be the clearer signal that the expanding discovery corpus is converting into executable agent commerce.
Sources
- Commits · x402-foundation/x402 · GitHub
- The 2026-07-28 MCP Specification Release Candidate | Model Context Protocol Blog
- Pull requests · modelcontextprotocol/modelcontextprotocol · GitHub
- IXOPAY's Agentic Suite for Merchants Supports New Buying Experiences
- Mastercard gives merchants a simpler way to build, connect and scale AI-powered shopping experiences
- Agent Control Standard (ACS) - OWASP Gen AI Security Project
- ToolGuardian: Declarative Security for AI Agent-Tool Interactions
- Transparency obligations under Article 50 of the AI Act | Shaping Europe’s digital future
- Singapore Launches New Model AI Governance Framework for Agentic AI | IMDA
- x402 repository activity
- MCP release notes
- MCP roadmap
- MCP pull requests
- IXOPAY announcement
- Mastercard announcement
- OWASP Agent Control Standard
- ToolGuardian paper
- European Commission guidance
- IMDA framework announcement
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
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
How we know they take payment
343 of 4,782
payment-labelled agents (7.2%) 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.
Newly indexed agents per week, by payment label
Changes reflect both ecosystem activity and changes in crawler source coverage.
A few settlement wallets receive most of the money.
Across 1,286 earning wallets backing 2,512 linked services, the distribution is heavily power-law. Wallet-level Gini and HHI avoid multiplying transfers when several catalog entries share one recipient.
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-09-15. 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-09-15},
year = {2026}
}
<iframe src="https://agenstry.com/reports/state-of-agent-economy" width="100%" height="900" frameborder="0"></iframe>
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.
Weekly State of the Agent Economy
Top earners · biggest 7-day movers · payment-rail adoption · methodology, straight from our index. Free, Mondays.