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-09-08 21:01:03 UTC methodology JSON CSV cite this archive
Weekly briefing · 2026-W37 archived view
Sep 7, 2026

Agenstry’s observed agent web expanded materially in ISO week 2026-W37: 8,041 candidates were indexed, up +559.00 (+7.5%) week on week; the live, introspectable layer reached 734, up +140.00 (+23.6%); and 2,486 agents showed inbound stablecoin settlement over the measured 30-day window, up +286.00 (+13.0%). The central qualification is commercial depth: observed 30-day gross settlement was 244999.43 USD, but revenue remained highly concentrated, with the top agent accounting for 72.9% and the top ten for 95.6%.

Market structure: more endpoints, still a thin verified runtime layer

The funnel continues to show the difference between discoverability and operational readiness. Of 8,041 indexed candidates, 6,475 returned a parseable card, while 734 were live JSON-RPC or introspectable MCP endpoints. Only 98 published a JWS-signed card. That makes signed identity the narrowest measured layer of the agent web, even as endpoint discovery accelerates.

The paid surface is broader than runtime verification. Agenstry labels 4,397 payment-capable records, but only 335 are self-declared live through an endpoint that returned an unpaid HTTP 402 challenge or served a /.well-known/x402 manifest; the stated measurement defines runtime payment challenges as authoritative. The implication for buyers, registries and regulators is straightforward: catalog presence should remain distinct from a tested ability to quote, authenticate and settle a transaction.

Labelled payment-capable records by protocol4.4Kx4024.2K · 96.5%MPP88 · 2.0%A2A+x40240 · 0.9%AP221 · 0.5%L4024.00 · 0.1%Stripe SPT1.00 · 0.0%

x402 remains the default settlement vocabulary in the labelled corpus, with 4,243 records, versus 88 for MPP, 40 for A2A+x402 and 21 for AP2. The ISO week 2026-W37 cohort is necessarily incomplete as of the 2026-09-07T13:30:42.229154+00:00 measurement time: it contains 37 additions, all x402-labelled, and should not be read as a full-week deceleration from the 406 additions recorded for 2026-W36.

Where the money is flowing

The revenue distribution is more concentrated than the growth figures alone imply. Across 2,486 earning agents and 1,256 earning wallets, observed 30-day gross settlement was 244999.43 USD; the median was 0.26 USD, while the p95 was 44.6397 USD. The Gini coefficient was 0.994, and the HHI rose from 4,934.10 to 5,487.40, a +553.30 (+11.2%) week-on-week increase.

That pattern is consistent with an early market in which a small number of endpoints capture most recorded settlement while a long tail tests pricing, distribution and machine-payable interfaces. The highest-priority demand gap remains audio transcription: Agenstry records 231 variants against 663 unique sources, a 50% unmet share and a 2264.7% rising trend. This is an actionable gap because it is a bounded, readily benchmarked service with a clear per-call pricing model rather than a general-purpose agent category.

Spec and protocol: production concerns are moving from connectivity to operability

MCP’s most consequential recent change remains the final 2026-07-28 specification: it removes protocol-level sessions and initialization, uses self-describing requests, adds header-based routing and cacheable list responses, formalizes extensions, and hardens authorization. The maintainers’ subsequent roadmap prioritizes agentic messaging, HTTP-native transport, identity and enterprise security, suggesting that implementation consistency—not a new core transport—is now the central standards problem. MCP’s July specification announcement and its August roadmap support that reading. (github.com)

On payments, the x402 codebase recently introduced a settlement_pending outcome for transactions broadcast but not yet confirmed, allowing clients to reconcile an uncertain transaction rather than treating it as a terminal failure. The official changelog also records security fixes to payment-gate route matching. (github.com) A reported issue opened on September 1 alleges that Coinbase’s hosted facilitator rejected previously settling Solana exact-payment envelopes following a configuration or deployment change; it remains an open issue, not a confirmed protocol-wide defect. The issue record is nevertheless a useful reminder that live facilitator behaviour must be separately probed from SDK conformance. (github.com)

Notable deployments and research

Enterprise launches this week favoured governed, domain-specific workflow agents rather than open agent marketplaces. CBTS launched Forge Agents for mid-market deployment and management on September 1, while ProcessUnity introduced agents for third-party risk-management work that retains human judgment for escalation. CBTS’s launch announcement and ProcessUnity’s release underline the commercial premium placed on security, operational control and bounded authority. (cbts.com)

Research is converging on the same implementation constraint. A September 4 review argues that interoperability layers such as MCP and A2A improve connection between systems but do not themselves establish trustworthy delegation, emphasizing provenance, bounded authority, failure detection and recovery. “From Language Models to World-Acting Systems” is a useful synthesis for purchasers assessing whether an “agent-ready” interface actually supports accountable action. (arxiv.org)

Regulation

The regulatory direction is toward auditable control of delegated actions. The EU AI Act’s general application date was 2 August 2026, although subsequent EU legislation delays specified high-risk-system obligations; firms selling agents into Europe should distinguish those timelines rather than assume a single compliance date. EUR-Lex’s AI Act summary and Regulation (EU) 2026/1744 set out the split. (eur-lex.europa.eu) In the United States, reporting this week identified a proposed Stop Rogue AI Act focused on NIST standards and deployment practices for AI agents; it should be treated as an early legislative signal rather than operative law. Axios’s report provides the current public account. (axios.com)

What to watch next week

The key test is whether the gain in live endpoints converts into more authoritative payment evidence: specifically, whether the count of agents producing observed HTTP 402 challenges rises alongside the broader index. Investors and operators should also monitor resolution of the hosted-facilitator issue, because settlement reliability—not discovery volume—is the near-term constraint on recurring agent-to-agent commerce.

Sources

  1. modelcontextprotocol/blog/content/posts/2026-07-28-spec-ga/index.md at main · modelcontextprotocol/modelcontextprotocol · GitHub
  2. x402/python/x402/CHANGELOG.md at main · x402-foundation/x402 · GitHub
  3. Hosted x402 facilitator: exact-SVM compute-limit ceiling tightened into a ~20k–100k band (Aug 23–26), rejecting spec-shaped envelopes; reason diverges from OSS main · Issue #795 · coinbase/cdp-sdk · GitHub
  4. CBTS Launches Forge Agents to Deliver Custom AI Agents in Days
  5. From Language Models to World-Acting Systems: Progress and Limits of Agentic AI across Digital, Social, Virtual, and Physical Environments
  6. Rules for trustworthy artificial intelligence in the EU | EUR-Lex
  7. Exclusive: New bill cracks down on AI agents after Hugging Face breach
  8. MCP’s July specification announcement
  9. August roadmap
  10. The official changelog
  11. The issue record
  12. CBTS’s launch announcement
  13. ProcessUnity’s release
  14. “From Language Models to World-Acting Systems”
  15. EUR-Lex’s AI Act summary
  16. Regulation (EU) 2026/1744
  17. Axios’s report
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 8,102
100.0%
Every candidate we have seen across every source.
Valid card 6,535
80.7%
Returned a parseable A2A/MCP card on probe.
Live 738
9.1%
Live JSON-RPC / introspectable MCP.
Signed 98
1.2%
Card published with a JWS signature.
Earning (30d) 2,474
30.5%
Agents where we observed inbound USDC/EURC settlement to their declared x402 payTo wallet. Measured over the wallets scanned so far (1772 of 1835 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,633 546 15.0%
agentic_market 3,346 84 2.5%
recrawl_warm 2,835 175 6.2%
cdp_discovery 1,875 49 2.6%
mcp_registry 1,747 280 16.0%
manifests 1,249 169 13.5%
github_code 871 83 9.5%
x402_list 597 35 5.9%
lists 504 29 5.8%
registry 503 318 63.2%
recrawl_cold 290 2 0.7%
a2aregistry 252 209 82.9%
n8n_workflows 222 0 0.0%
github_topics 156 5 3.2%
a2a_registry_org 155 64 41.3%
3a · By protocol kind

A2A vs MCP vs paid_api

paid_api
4,249
a2a_agent
2,259
workflow
95
a2a
27
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,297
mpp
89
a2a_x402
40
ap2
21
l402
4
stripe_spt
1
3b · Evidence grade

How we know they take payment

335 of 4,452 payment-labelled agents (7.5%) 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,672
Catalog listing
1,006
Agent card
332
Live 402 challenge
240
Official protocol directory
87
/.well-known/x402
86
Not re-probed yet
20
mpp_challenge
8
mpp_manifest
1
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-W25 · ap2: 1 2026-W25 · x402: 5 25 2026-W26 · a2a_x402: 1 2026-W26 · ap2: 1 2026-W26 · x402: 5 2026-W27 · a2a_x402: 4 2026-W27 · x402: 9 27 2026-W28 · a2a_x402: 5 2026-W28 · l402: 1 2026-W28 · x402: 1140 2026-W29 · a2a_x402: 2 2026-W29 · ap2: 1 2026-W29 · mpp: 1 2026-W29 · x402: 244 29 2026-W30 · a2a_x402: 2 2026-W30 · mpp: 4 2026-W30 · x402: 296 2026-W31 · a2a_x402: 2 2026-W31 · ap2: 1 2026-W31 · mpp: 81 2026-W31 · x402: 262 31 2026-W32 · a2a_x402: 10 2026-W32 · ap2: 2 2026-W32 · x402: 219 2026-W33 · a2a_x402: 4 2026-W33 · ap2: 3 2026-W33 · x402: 225 33 2026-W34 · a2a_x402: 1 2026-W34 · ap2: 1 2026-W34 · x402: 260 2026-W35 · a2a_x402: 1 2026-W35 · ap2: 1 2026-W35 · mpp: 2 2026-W35 · x402: 242 35 2026-W36 · a2a_x402: 2 2026-W36 · x402: 404 2026-W37 · x402: 91 37
a2a_x402 ap2 l402 mpp x402
4 · Inflow concentration · 30d

A few settlement wallets receive most of the money.

Across 1,265 earning wallets backing 2,474 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
$245583.39
Recipient wallets
1,265
Median · wallet
$0.260
p95 · wallet
$44.86
Top 1 share
72.8%
Top 5 share
93.1%
Gini
0.994
extreme inequality
HHI
5461
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-08-10 peak 128/day 2026-09-08
New agents · 30d
+1,886
Earning agents · 30d
2,579
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 50% 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-09-08. 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-09-08},
  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.