AgentIndex · traderszone

Trends · Report

Builder Demand Report

What builders are asking for, measured against what actually exists. Regenerated from a nightly-mined corpus of developer questions, forum discussion and search demand, then crossed against our own probe-measured index of live endpoints.

Generated 2026-08-22T19:28:02.034Z · window 7 days · 372 signals · corpus of 372 since 2026-08-17

This week

Demand in the last 7 days is led by multi-agent orchestration, skills and memory: 37 of 331 signals, recurring 201 times. Supply has not kept pace — 120 of 3830 measured MCP servers (3.1%) expose a matching tool, 116 of them answering right now. Second is agent payments and commerce (30 signals). Version activity was observed across 5 projects, led by modelcontextprotocol/servers.

Leading themes

  • Multi-agent orchestration, skills and memory — 37 signals, recurring 201 times. Supply: 120 of 3,830 measured servers (3.1%).
  • Agent payments and commerce — 30 signals, recurring 202 times. Supply: 454 of 3,830 measured servers (11.9%).
  • New MCP server launches — 30 signals, recurring 180 times.
  • Learning and getting started — 27 signals, recurring 205 times.
  • Practitioner adoption and governance — 11 signals, recurring 82 times.
  • Deployment, cost and reliability — 11 signals, recurring 71 times.

Where demand outruns supply

Supply is counted only where a tool name reliably implies the capability. Themes without a figure are ones where any ratio would measure a common word rather than a real feature.

  • Multi-agent orchestration, skills and memory — demand rank 1, supply 3.1% of measured servers (116 answering now).
  • Agent payments and commerce — demand rank 2, supply 11.9% of measured servers (445 answering now).
  • Agent control of browsers and computers — demand rank 7, supply 1.3% of measured servers (48 answering now).
  • Scraping, extraction and research — demand rank 9, supply 6.6% of measured servers (251 answering now).

Current versions observed

An inventory of what is current, not a changelog — our feed records when we observed a version, not when it shipped. Useful for checking whether a pin is behind.

  • modelcontextprotocol/servers — 10 versions observed, latest servers Release 2026.8.18
  • a2aproject/A2A — 10 versions observed, latest A2A v1.0.1
  • coinbase/x402 — 10 versions observed, latest x402 [email protected]
  • modelcontextprotocol/modelcontextprotocol — 9 versions observed, latest modelcontextprotocol 2026-07-28
  • google-agentic-commerce/AP2 — 2 versions observed, latest AP2 v0.2.0

What the paid report adds

This page is the summary. The full report returns every theme with the underlying signals as evidence (source, URL, recurrence, engagement), a stated implication per theme, the complete supply-gap table, the full version inventory, and the caveats as structured fields so an agent quoting us carries them.

Free shallow preview, no payment: https://agents.traderszone.net/demand/preview

How to buy it

The report costs $0.05 per call in USDC on Base, paid with x402. There is no account, no API key, no invoice and no subscription. Native USDC only — bridged USDC.e and USDbC do not implement EIP-3009 and cannot be used.

The exchange is three steps:

  1. Call GET https://agents.traderszone.net/demand.
  2. Receive 402 Payment Required with the payment terms in the body — amount, network, asset, recipient.
  3. Call again with an X-PAYMENT header carrying the signed authorization. You are served, and the settlement transaction hash comes back in X-PAYMENT-RESPONSE.

You pay no gas: settlement is broadcast by us. Full machine-readable terms for every priced route: https://agents.traderszone.net/.well-known/x402

How to wire it into an agent

Over MCP. Add one server entry to your MCP client — Claude Desktop, Claude Code, Cursor, or any Streamable HTTP client:

{
  "mcpServers": {
    "agentindex": {
      "url": "https://agents.traderszone.net/mcp"
    }
  }
}

Then call the tool get_demand_report. Called without a payment argument it returns the payment terms; called with one it returns the report. Two tools on the same server are free and need no payment at all: search_agents and get_agent_profile.

Over plain HTTP. Any x402 client library works, or implement the three steps above directly.

Patterns worth stealing. Call it weekly and feed the gaps array into whatever decides your roadmap — it is the shortest path from "what is asked for" to "what nobody has built". Or check the version inventory in CI and fail the build when a dependency you pin has moved.

Caveats

  • The demand corpus began 2026-08-17 and holds 372 signals. It is young; treat trend direction as indicative, not established.
  • Autocomplete queries measure search-suggestion frequency, not distinct people. They indicate what is commonly asked, not how many ask it.
  • Themes are matched against signal titles only, not bodies. This is stricter and leaves more signals unclassified, but it stops incidental words in marketing copy from registering as demand.
  • Signals may match more than one theme, so theme counts sum to more than the corpus.
  • Supply counts come only from servers whose tool lists we captured by handshake (3830); servers we could not handshake are excluded rather than assumed absent.
  • Themes are matched by a published keyword taxonomy, not by a language model, so the same input always yields the same report.
  • Release rows record when we observed a version, not when it was published. Treat the release section as a current-version inventory, not a changelog.
  • Supply is measured only for themes where a tool name reliably implies the capability. Themes with no supply figure are ones where any ratio would measure a common word rather than a real feature.

AgentIndex Builder Demand Report, https://agents.traderszone.net/reports/demand (CC-BY-4.0)