Skip to content
x402 logo

x402

Open HTTP payment standard where servers add one middleware line to demand per-request payment and clients pay via 402 responses.

Actively maintained

AI agent paymentsFinanceFor developersOpen source
x402.org ↗
Open x402.orgAlternativesSet it up for my team
x402: data, price, alternatives
At a glancechecked Nov 3, 2026

6.8k ★

Use not read yet

For
API providers and AI agent builders who want to charge per request with stablecoin payments over HTTP
Activity
Actively maintainedrelease today · site updated 6 days ago
How it runs
SDK
Used for
  • add payment requirements to API endpoints
  • let AI agents pay for API access
  • monetize paywalled digital content per request
Worth knowingcomputed from what we read · each with its source
  • On the web since 2025, older than 67% of its shelfINITE Atlas
  • 6,793 stars on GitHubGitHub ↗
  • Publishes llms.txt, a file written for AI assistantsx402.org ↗
Alternatives in AI agent paymentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare x402 with

Pick up to two.

All 10 alternatives to x402 →

All AI agent payments tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use x402 for?

Sign in to leave a note
Questions this page answers
  • What is x402?

    Open HTTP payment standard where servers add one middleware line to demand per-request payment and clients pay via 402 responses. It is listed in the Atlas under AI agent payments, Finance.

  • Who is x402 for?

    API providers and AI agent builders who want to charge per request with stablecoin payments over HTTP

  • Is x402 still maintained?

    Actively maintained: release today · site updated 6 days ago.

  • What are alternatives to x402?

    In AI agent payments, by use: Purchase API by Agentcard, Bursora, Squid Pay, Pay 2 Cash, Agorean.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk