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-10-03 18:47:40 UTC methodology JSON CSV cite this archive
Weekly briefing · 2026-W32 archived view
Aug 3, 2026

The agent economy entered August with a sharper split between discovery, runtime availability, and monetisation. Agenstry’s indexed corpus reached 5,855, up 19.1% from 4,918 in 2026-W30, while live agents rose 20.2% to 386; the more consequential change was in observed settlement, where earning agents increased from 21 to 1,060 as wallet coverage expanded. At the same time, revenue concentration became materially more severe: the Gini coefficient reached 0.964, with the top agent accounting for 72.1% of gross 30-day volume.

Where the money is flowing

The corpus now records $142,593.8 in gross 30-day settlement across 1,060 earning agents, but the distribution is closer to a winner-take-most market than a broad base of independent suppliers. The median agent received $1.53, compared with $124.726 at the 95th percentile; the top five agents captured 83.1% of volume and the top ten 83.9%. HHI reached 5,241.0, up from 1,495.80 in 2026-W30.

30-day agent-economy revenue concentrationTop 172Top 583Top 1084

The week-over-week jump in earning agents should not be read as equivalent to a 49-fold expansion in underlying demand. Agenstry states that settlement was observed over 1,314 of 2,218 wallets with a wallet, and the metric is therefore measured over scanned wallets rather than the ecosystem as a whole. The data nevertheless establish a useful distinction for investors and regulators: monetisation is now observable at scale, but it is highly concentrated and still sensitive to measurement coverage.

The payment layer remains dominated by x402, with 2,879 records, versus 82 for MPP, 17 for AP2, and 2 for L402. The newest protocol cohort, 2026-W32, contains 17 records, all x402, while the preceding 2026-W31 cohort included 81 MPP records alongside 257 x402 records. That suggests experimentation with alternative payment rails, but not yet a durable shift in the installed base.

Spec & protocol

The most significant external protocol event was the July 28, 2026 MCP specification release. The release introduces a stateless operating model over commodity HTTP, formalises an extensions track, and adds a Tasks lifecycle in which clients can create, inspect, update, and cancel long-running work through task handles. The official MCP announcement describes the release as a stability point for implementers building against the 2026-07-28 specification. MCP specification release

A2A also moved closer to a more mature governance and implementation phase. The official A2A community hub flagged an upgrade on July 26, while Oracle documented a July 7 capability allowing external A2A-compatible clients to discover and call Select AI agent teams through standard HTTPS interfaces. A2A community updates Oracle A2A release note

For Agenstry, the practical implication is that conformance testing will increasingly need to distinguish between a static card, a reachable endpoint, and a service that correctly implements asynchronous or stateful protocol semantics. The current funnel makes that gap visible: 4,307 entries have a valid card, but only 386 are live, and just 50 publish a JWS signature.

Notable launches and capital

Enterprise adoption continued to move through infrastructure and control planes rather than consumer-facing autonomous workers. Abrigo announced its Agentic Platform Experience for financial institutions, targeting lending workflows and governance requirements, with a Q3 2026 launch plan. Abrigo Agentic Platform Experience

Security and observability attracted a notable financing event: Neo emerged from stealth with $100 million backed by Andreessen Horowitz and Bessemer Venture Partners, positioning itself around inventory, attribution, posture intelligence, and policy enforcement for agentic software. Neo funding announcement

The pattern is consistent with Agenstry’s measurements. The ecosystem is adding inventory rapidly—2,651 new agents in the last 30 days, compared with 1,834 in the prior comparison period—but the scarce asset is not listing volume. It is verified runtime access, payment identity, attribution, and evidence that an agent can operate predictably inside enterprise controls.

Research

Recent research is shifting from abstract coordination toward institutional infrastructure. A July paper, Underwriting the Agent Economy: The Blueprint for an AI Insurance Stack, frames insurance as a missing layer for systems that transact and act with limited human intervention. Underwriting the Agent Economy

A separate July paper on regulating autonomous and agentic AI compares regulatory approaches across content platforms, data protection, financial services, and the EU AI Act. Regulating autonomous and agentic AI The common thread is operational traceability: who delegated an action, which agent executed it, what tools and counterparties were involved, and whether a human could intervene.

Regulation

The EU moved from framework-setting to operational enforcement. The European Commission published guidance on transparency obligations that began applying on August 2, 2026, and its AI Act Service Desk states that agents intended to interact with natural persons or generate content fall within the relevant transparency rules. European Commission transparency guidance EU AI Act Service Desk on agents

The policy burden is therefore moving toward evidence. Agenstry’s distinction between self-declared live status—221 entries, or 7.4% of labelled records—and runtime challenges is increasingly aligned with what regulated deployments will require: machine-readable identity, auditable action histories, and independently testable claims about capability.

What to watch next week

The key signal will be whether the MCP 2026-07-28 release produces a measurable increase in live, task-capable endpoints rather than another wave of static declarations. Agenstry should also track whether the recent MPP cohort persists after 2026-W31 or reverts toward the x402-heavy pattern visible in 2026-W32.

Sources

  1. MCP specification release
  2. A2A community updates
  3. Oracle A2A release note
  4. Abrigo Agentic Platform Experience
  5. Neo funding announcement
  6. Underwriting the Agent Economy
  7. Regulating autonomous and agentic AI
  8. European Commission transparency guidance
  9. EU AI Act Service Desk on agents
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 10,989
100.0%
Every candidate we have seen across every source.
Valid card 7,187
65.4%
Returned a parseable A2A/MCP card on probe.
Live 1,156
10.5%
Live JSON-RPC / introspectable MCP.
Signed 137
1.2%
Card published with a JWS signature.
Earning (30d) 1,659
15.1%
Settlement wallets where we observed inbound USDC to the x402 payTo address declared by an indexed agent, one count per wallet (3093 linked services). Measured over the wallets scanned so far (2171 of 2284 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 5,543 1,107 20.0%
recrawl_warm 5,146 249 4.8%
agentic_market 4,093 143 3.5%
cdp_discovery 2,895 109 3.8%
manifests 2,068 578 27.9%
mcp_registry 1,747 292 16.7%
n8n_workflows 1,147 0 0.0%
github_code 894 100 11.2%
x402_list 836 57 6.8%
smithery 693 170 24.5%
registry 672 478 71.1%
a2aregistry 569 473 83.1%
lists 542 62 11.4%
recrawl_cold 290 3 1.0%
a2a_registry_org 275 124 45.1%
3a · By protocol kind

A2A vs MCP vs paid_api

paid_api
4,447
a2a_agent
2,742
workflow
1,147
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
4,628
mpp
125
a2a_x402
56
ap2
32
l402
4
stripe_spt
1
stripe_acp
1
3b · Evidence grade

How we know they take payment

1,681 of 4,847 payment-labelled agents (34.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
1,897
Live 402 challenge
1,304
Catalog listing
640
Agent card
546
/.well-known/x402
318
Official protocol directory
83
mpp_manifest
34
mpp_challenge
25
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-W28 · a2a_x402: 1 2026-W28 · x402: 18 28 2026-W29 · a2a_x402: 2 2026-W29 · ap2: 1 2026-W29 · mpp: 1 2026-W29 · x402: 191 2026-W30 · a2a_x402: 2 2026-W30 · x402: 243 30 2026-W31 · a2a_x402: 2 2026-W31 · ap2: 1 2026-W31 · mpp: 85 2026-W31 · x402: 214 2026-W32 · a2a_x402: 9 2026-W32 · ap2: 2 2026-W32 · mpp: 2 2026-W32 · x402: 189 32 2026-W33 · a2a_x402: 4 2026-W33 · ap2: 4 2026-W33 · mpp: 5 2026-W33 · x402: 157 2026-W34 · a2a_x402: 1 2026-W34 · ap2: 1 2026-W34 · mpp: 4 2026-W34 · x402: 207 34 2026-W35 · a2a_x402: 2 2026-W35 · ap2: 2 2026-W35 · mpp: 1 2026-W35 · x402: 199 2026-W36 · a2a_x402: 3 2026-W36 · mpp: 1 2026-W36 · stripe_acp: 1 2026-W36 · x402: 340 36 2026-W37 · a2a_x402: 4 2026-W37 · mpp: 3 2026-W37 · x402: 303 2026-W38 · a2a_x402: 1 2026-W38 · mpp: 3 2026-W38 · x402: 229 38 2026-W39 · a2a_x402: 4 2026-W39 · ap2: 2 2026-W39 · x402: 323 2026-W40 · a2a_x402: 2 2026-W40 · ap2: 7 2026-W40 · mpp: 7 2026-W40 · x402: 456 40
a2a_x402 ap2 mpp stripe_acp x402
4 · Inflow concentration · 30d

A few settlement wallets receive most of the money.

Across 1,659 earning wallets backing 3,093 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
$852760.48
Recipient wallets
1,659
Active sellers · 30d
1,347
Median · wallet
$0.410
p95 · wallet
$106.00
Top 1 share
73.6%
Top 5 share
87.4%
Gini
0.994
extreme inequality
HHI
5476
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-09-04 peak 652/day 2026-10-03
New agents · 30d
+3,184
New earning wallets · 30d
789
first observed earning in the last 30 days

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-10-03. 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-10-03},
  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.