x402 Adoption: npm Downloads of the HTTP 402 Payment Standard

Home › Guides › x402 npm Downloads

✓ checked 20 October 2026 · source: npm and PyPI download statistics, retrieved 20 October 2026 · monthly table · method · download the data

x402, an open standard that lets websites and APIs charge per request, is being installed far more often than a year ago. Its main npm package, x402, was downloaded 1,880,802 times in the 30 days to 18 October 2026, about 20 times as often as in the same 30 days of 2025 (95,164). Its newer core library, @x402/core, had 1,439,489 downloads in the same period.

1,880,802 npm downloads in 30 days20× the same period last year605+ npm packages named after x402204,765 PyPI downloads last month

What x402 is

HTTP, the protocol behind the web, has had a status code for payments since the 1990s: 402 Payment Required. It was reserved for future use and rarely used. x402 puts it to work. The project’s README describes x402 as “an open standard for internet native payments” that aims to support “all networks (both crypto & fiat)”. In the typical flow it describes, a client asks for a resource, the server answers with a 402 Payment Required status and the payment details it accepts, the client sends a signed payment with its next request, and a separate “facilitator” service verifies and settles the payment before the server returns the content.

The first x402 package appeared on npm on 20 February 2025; Coinbase also publishes its own package, @coinbase/x402. A second generation of packages, under the @x402/ name and published from the x402 Foundation’s repository, arrived on 10 and 11 December 2025, split into a core library, blockchain-specific parts and add-ons for web frameworks.

Why it matters for crawlers and agents

Websites that don’t want AI crawlers have mostly had one tool: refuse them, by robots.txt or at the server. x402 is one of several attempts to offer a third option besides “allow” and “block”: charge. A server can answer an automated client with a price instead of a refusal, and an AI agent that holds a wallet can pay and continue without a human signing up for an account. That is why download numbers for x402 are a rough signal of interest in paid machine access to the web. For how AI companies and websites currently block crawlers, see which AI companies block rivals’ crawlers and our AI-crawler census.

Downloads by month

Monthly downloads of the x402 package rose every month from its first downloads in February 2025. September 2026 had 1,729,207, about 37 times September 2025 (46,502).

Monthx402 npm downloads
Feb 202560
Mar 2025157
Apr 20251,359
May 20254,696
Jun 20259,899
Jul 202515,659
Aug 202529,699
Sep 202546,502
Oct 2025139,092
Nov 2025165,887
Dec 2025239,456
Jan 2026317,057
Feb 2026398,840
Mar 2026630,795
Apr 2026734,759
May 20261,035,111
Jun 20261,110,655
Jul 20261,399,799
Aug 20261,545,242
Sep 20261,729,207

The most-downloaded x402 packages

The original x402 package is still the most downloaded, although its latest version, 1.2.0, dates from 16 April 2026 and new development happens in the @x402/ packages, which reached version 2.28.0 in September. Many projects pull in a package indirectly, as a dependency of another one, so the same install can count towards several packages.

PackageWhat it isDownloads, 19 Sep – 18 Oct 2026
x402Original package (version 1)1,880,802
@x402/coreCore library (version 2)1,439,489
@x402/evmPayments on Ethereum-compatible blockchains955,083
@x402/extensionsOptional extensions600,248
@x402/fetchAdds payments to fetch requests (clients)530,332
@x402/svmPayments on Solana335,901
@coinbase/x402Coinbase’s package287,415
@x402/honoServer middleware for Hono180,295
@x402/expressServer middleware for Express116,552
@x402/nextServer middleware for Next.js90,416

Beyond these, at least 605 npm packages have x402 in their name, and 97 of them had at least 1,000 downloads in the period; most are third-party tools, payment services and AI-agent add-ons. On PyPI, the Python package x402 had 204,765 downloads in the last month, according to pypistats.

What this doesn’t show

  • Downloads aren’t users or payments. Automated builds and test runs download packages over and over, and one project can trigger many downloads.
  • Package numbers overlap, because packages depend on one another; adding them up overstates use.
  • Download counts say nothing about how much money moves through x402 or who is paying for what.

Method

On 20 October 2026 we requested daily download counts for the x402 package from the npm downloads API for 1 October 2024 to 19 October 2026, and last-month totals (19 September to 18 October 2026) for every package returned by an npm registry search for “x402” (the search returns at most 1,000 results; we kept those with x402 in the name). Monthly figures sum the daily counts; October 2026 is left out because it was incomplete. Package creation and version dates come from the npm registry. The PyPI figure is pypistats’ last-month total for x402. A separate script recomputes every number from the saved API responses.

Download the data

Cite as: ProxyPicker, “x402 Adoption: npm Downloads of the HTTP 402 Payment Standard”, 20 October 2026, https://proxypicker.com/x402-npm-downloads/.

Related: AI companies and rival crawlers · robots.txt AI preferences · The anti-bot bypass economy.

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.