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-19 16:21:45 UTC methodology JSON CSV cite this archive
Weekly briefing · 2026-W33 archived view
Aug 10, 2026

The decisive signal in 2026-W33 is not discovery volume but the gap between discoverability, runtime availability and monetisation. Agenstry indexed 6204 candidates, up +349.00 (+6.0%) week on week, while live endpoints rose to 435, up +49.00 (+12.7%); observed earning agents rose more sharply to 1467, up +407.00 (+38.4%). Yet the revenue base remains exceptionally concentrated: the top one agent accounts for 83.5% of observed 30-day gross settlement, while the Gini reached 0.994 and HHI 7032.4.

Measurement: discovery is scaling faster than verifiable operations

The corpus now contains 6204 indexed candidates. Of those, 4657 returned a parseable A2A/MCP card, 435 were live JSON-RPC or introspectable MCP endpoints, and 55 published a JWS-signed card. The practical implication is that agent discovery remains considerably ahead of deployable, authenticated runtime infrastructure: a large share of supply can describe itself, but far fewer services can be reached and interrogated as functioning agent endpoints.

Agenstry agent funnel, 2026-W33Indexed6.2KValid card4.7KLive435Signed55Earning (30d)1.5K

The largest directly productive cohort is not identical to the live-endpoint cohort. 1467 agents were observed receiving inbound USDC/EURC settlement to declared x402 pay-to wallets over the 30-day window, measured across 1177 scanned wallets out of 1289 scannable wallets. That is a wallet-observation measure rather than an ecosystem-wide revenue census, and should not be read as evidence that every earning endpoint is currently introspectable.

Source quality is also uneven. 3227 protocol-labelled records exist, but only 233, or 7.2%, are self-declared live through an unpaid HTTP 402 challenge or a /.well-known/x402 manifest; runtime payment challenges remain the stronger operational signal. The high live rates in a2aregistry (77.2) and registry (54.4) contrast sharply with cold recrawls (0.4) and n8n workflows (0.0), suggesting that curated directories are more useful for verification than indiscriminate catalog ingestion.

Where the money is flowing

Observed gross settlement over the trailing 30 days was 123086.13 across 1467 earning agents and 695 earning wallets. The median agent recorded 0.2, versus 34.8073 at the 95th percentile. The top five agents captured 96.3% of gross settlement and the top ten 97.2%. This is not yet a broad-based services market: it is an early transactional network with a very small number of dominant settlement destinations.

Concentration has intensified since 2026-W32. The supplied week-over-week Gini delta is +0.03 (+3.1%), and HHI increased +1,791.40 (+34.2%). That pattern matters more than the headline rise in earning-agent observations. It indicates that new wallets and declared payment endpoints are appearing more rapidly than independently scaled demand is being distributed across suppliers.

Two demand gaps stand out. “Image generation” is labelled active, with 3 variants, 30 unique sources and 56% unmet demand. “Bitcoin payment” is labelled very active, with 34 variants, 93 unique sources and 49% unmet demand. Both are potentially attractive categories for new supply, but the difference between observed agent counts and concentrated settlement argues for validating paid execution—not merely publishing cards or catalog entries—before underwriting a market opportunity.

Spec & protocol

x402 remains the dominant payment declaration in the corpus, with 3103 records, compared with 84 for MPP, 19 for AP2, 17 for A2A+x402, 3 for L402 and 1 for Stripe SPT. In the 2026-W33 cohort, 18 of 21 records were x402 and 3 AP2. This should be treated cautiously: the W33 data is as of 2026-08-10T13:29:28.676666+00:00, so it represents the opening portion of the ISO week rather than a completed seven-day comparison with W32’s 225 total.

The consequential external protocol event remains MCP’s 2026-07-28 release. It replaces the protocol’s session-oriented core with stateless request/response operation, introduces Multi Round-Trip Requests for server-to-client interaction, adds header-based routing, cacheable list results, an extensions framework and authorization changes around issuer validation and client metadata. The design should lower the operational friction of horizontally scaling remote MCP servers, while requiring operators to manage a non-trivial migration away from session assumptions. MCP’s release notes and GitHub’s early support announcement indicate that ecosystem adoption is already moving ahead of the official release date. (blog.modelcontextprotocol.io)

A2A’s institutional footing continues to matter for discovery: the protocol is now housed within the Linux Foundation project structure and includes official SDKs, sample implementations, an inspector and a technology-compatibility kit. The project’s public repository frames A2A as an interoperability layer for independent agent systems, rather than a payment or governance standard. (github.com)

Regulation and enterprise controls

The regulatory clock has become more concrete. The European Commission’s AI Act Service Desk says that, from 2 August 2026, Article 50 transparency rules apply where AI agents are intended to interact with natural persons or generate content; it also states that agents are covered through the Act’s existing definitions rather than through a standalone legal category. The Commission guidance makes agent identity, disclosure and evidence trails more than voluntary design features for customer-facing deployments. (ai-act-service-desk.ec.europa.eu)

Payments standards are moving in the same direction. Google transferred AP2 to the FIDO Alliance in April, positioning the protocol within a broader standards body focused on secure authentication; AP2’s model centres on proving the authority granted to an agent for a payment action. Google’s announcement is therefore strategically relevant to the Agenstry finding that payment declarations are common but signed service identities remain scarce. (blog.google)

What to watch next week

The key test is whether the MCP 2026-07-28 migration produces a measurable rise in genuinely live, challenge-verifiable services rather than another expansion in static cards and catalog listings. Particular attention should go to whether AP2 and MPP records gain runtime evidence, and whether the increase in earning-agent observations begins to diffuse beyond the small set of wallets currently dominating settlement.

Sources

  1. The 2026-07-28 Specification | Model Context Protocol Blog
  2. Agent2Agent (A2A) Project · GitHub
  3. How are AI agents addressed within the AI Act? | AI Act Service Desk
  4. Google donates Agent Payments Protocol to FIDO Alliance
  5. MCP’s release notes
  6. GitHub’s early support announcement
  7. The project’s public repository
  8. The Commission guidance
  9. Google’s announcement
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,692
100.0%
Every candidate we have seen across every source.
Valid card 5,153
77.0%
Returned a parseable A2A/MCP card on probe.
Live 493
7.4%
Live JSON-RPC / introspectable MCP.
Signed 62
0.9%
Card published with a JWS signature.
Earning (30d) 1,884
28.2%
Agents where we observed inbound USDC/EURC settlement to their declared x402 payTo wallet. Measured over the wallets scanned so far (1388 of 1462 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,104 370 11.9%
agentic_market 2,740 64 2.3%
recrawl_warm 2,434 167 6.9%
mcp_registry 1,601 215 13.4%
cdp_discovery 1,266 33 2.6%
manifests 852 90 10.6%
github_code 703 66 9.4%
lists 481 19 4.0%
x402_list 366 16 4.4%
registry 330 182 55.2%
recrawl_cold 290 2 0.7%
n8n_workflows 194 0 0.0%
github_topics 148 4 2.7%
a2aregistry 114 87 76.3%
smithery 89 10 11.2%
3a · By protocol kind

A2A vs MCP vs paid_api

paid_api
3,403
a2a_agent
1,885
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,421
mpp
83
a2a_x402
23
ap2
19
l402
3
stripe_spt
1
3b · Evidence grade

How we know they take payment

268 of 3,550 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
1,992
Catalog listing
967
Agent card
216
Live 402 challenge
192
Official protocol directory
82
/.well-known/x402
72
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: 7 22 2026-W23 · x402: 7 2026-W24 · ap2: 1 2026-W24 · l402: 1 2026-W24 · x402: 6 24 2026-W25 · a2a_x402: 1 2026-W25 · ap2: 2 2026-W25 · x402: 17 2026-W26 · ap2: 1 2026-W26 · x402: 6 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: 223 32 2026-W33 · a2a_x402: 4 2026-W33 · ap2: 3 2026-W33 · x402: 223 2026-W34 · x402: 110 34
a2a_x402 ap2 l402 mpp x402
4 · Inflow concentration · 30d

A few settlement wallets receive most of the money.

Across 910 earning wallets backing 1,884 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
$255334.18
Recipient wallets
910
Median · wallet
$0.264
p95 · wallet
$44.55
Top 1 share
70.0%
Top 5 share
94.3%
Gini
0.994
extreme inequality
HHI
5086
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-21 peak 331/day 2026-08-19
New agents · 30d
+1,735
Earning agents · 30d
1,893
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 55% 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-19. 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-19},
  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.