There is no honest headcount, but the tooling can be counted: as of August 11, 2026, a named basket of 9 agent-payment SDKs averages 653,587 downloads per week over a trailing four-week window, led by x402 at 344,595. Downloads include CI and mirror traffic, so read this as a directional adoption signal for agent-payment tooling, not as a number of people.
Nobody can count developers building agents, and any published headcount is a guess. What is countable is how often the tooling is installed: weekly download volume across a named basket of agent-payment SDKs. CI pipelines, mirrors and container rebuilds all inflate downloads, so this is a directional indicator of momentum rather than a population estimate.
It is still the most useful leading signal available. Tooling installs move before on-chain activity does — someone integrates the SDK weeks before their agent settles its first payment — so a sustained rise here tends to precede a rise in the measured figures elsewhere on this site.
Why the basket is named and small
The basket is listed explicitly so the figure can be recomputed and so its limits are visible. Packages that depend on one another are not summed into a single headline where that would double-count an install, and the per-package table below is the honest view. A broader basket would produce a larger number and a less meaningful one.
Also asked
Can you tell me how many developers are building AI agents?
Not credibly, and neither can anyone else — package registries do not expose unique installers. This page reports what is measurable, weekly download volume across a named SDK basket, and is explicit that CI and mirror traffic inflate it.
Cite this page
agent economy, “How many developers are building AI agents?”, agenteconomy.to/stats/how-many-developers-are-building-ai-agents, figures as of August 11, 2026 (UTC). Recomputable from agenteconomy.to/data.json.