x402-foundation/x402

A payments protocol for the internet. Built on HTTP.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 10th, 2026
Created on February 21st, 2025
Open Issues & Pull Requests: 539 (+0)
GitHub issues: Enabled
Number of forks: 2,028
Total Stargazers: 6,606 (+0)
Total Subscribers: 61 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.1 hours
Mean response time: 16.3 days
90th percentile: 59.8 days
Tracked items: 642

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 37% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 290
New in 7 days: 20
Closed in 7 days: 2
Avg open age: 138 days
Stale 30+ days: 179
Stale 90+ days: 111

Recent activity

Opened in 7 days: 17
Closed in 7 days: 2
Comments in 7 days: 4
Events in 7 days: 12

Top labels

  • enhancement (28)
  • bug (18)
  • documentation (2)
  • good first issue (2)
  • go (1)
  • python (1)

Detailed Description

x402 is a payments protocol that enables HTTP-based transactions on the internet.

The protocol addresses the problem of integrating payments into web services by building directly on HTTP semantics. Rather than requiring separate payment infrastructure or proprietary channels, x402 extends HTTP with payment-related headers and status codes, allowing servers to request payment and clients to fulfill those requests within the standard HTTP request-response cycle. This approach treats payment as a first-class concern of the web protocol itself, similar to how HTTP handles authentication and caching.

Developers should consider x402 for projects that need to monetize API access, gate content behind micropayments, or build services where payment flows naturally into the HTTP interaction. The protocol suits scenarios where lightweight, standards-based payment integration is preferable to bolting on external payment processors. It works best for services that want payment semantics embedded in the transport layer rather than handled separately at the application level.

The project shows active development with regular commits and ongoing refinement of the protocol specification. The codebase maintains focus on the core HTTP-based payment mechanism without scope creep into unrelated concerns. Documentation and examples are present to guide implementers, though the project remains in active evolution as the protocol matures.