Programmable payments for APIs and agents
A community-run view of the x402 ecosystem: what’s shipping and who’s building, and who’s using them. Organized, tagged, and backed by public signals.
The x402 ecosystem is evolving from early protocol implementations into a broader stack: services that monetize via per-request payments, client libraries that automate payment flows, facilitator services that simplify verification and settlement, and supporting layers for identity, permissions, and security. This release summarizes the current landscape, highlights developer momentum using public GitHub signals, and documents early real-world adoption patterns.
Key findings (this edition)
98
Ecosystem breadth is real
Distinct projects tracked across client integrations, service endpoints, facilitators, infrastructure, and tooling.
92%
Production is not hypothetical
Of cataloged projects report production users or live deployments, not just prototypes or demos.
7
Paid endpoints are growing
Service endpoints accept x402 payments today, spanning AI inference, data APIs, and compute.
1,800
Developer momentum is measurable
Active repositories in the past 90 days, based on public GitHub signals across the ecosystem.
15
Facilitator surface area is expanding
Facilitator services simplify verification and settlement, forming a critical middleware layer for the protocol.
Ecosystem
A tagged directory of x402 projects across endpoints, facilitators, tooling, integrations, and agent stacks.
- Category + role-in-flow tags
- Production vs experimental signal
- Links + short summaries
- Quick scan to find similar projects
Developer Report
A metrics-first view of x402 development using public GitHub signals across repos and integrations.
- Active contributors + Active repos
- Commit / PR / issue velocity
- Top repos by momentum
- Optional agent/MCP-slice trend
About x402 Guild
x402 Guild is a community-driven effort to maintain an open x402 dataset and a periodic “State of x402” report.