Pay Anything.
Instantly.
Programmatically.

Programmable payment infrastructure for APIs, AI agents and SaaS. Offchain authorization, onchain settlement, and a single HTTP status code standing between a request and its payment.

  • 402HTTP native
  • 1%Transaction fee
  • <$0.001Minimum payment
  • 0Subscriptions required

No account. No API key. No invoice. One round trip.

Built on open standards
HTTP 402 x402 Stablecoin settlement EVM networks Signed authorizations
The problem

Payments were designed for people, not software.

Selling an API today means assembling a stack that has nothing to do with your API. None of it works when the buyer is a machine.

Today The subscription tax

  • User registration and account management
  • Card processing, chargebacks and PCI scope
  • Monthly plans that under serve or over serve every customer
  • API keys to issue, rotate and revoke
  • A metering and billing system you have to build yourself
  • Minimum charges that make a $0.002 call impossible

An autonomous agent cannot sign up, accept terms or enter a card number. So it cannot buy anything.

With X Pay Payment as a protocol

  • Price set in one line of middleware
  • Payment authorized offchain, settled onchain
  • Charge per request, per second or per token
  • The payment is the credential, so there are no keys to manage
  • Metering, receipts and payouts handled for you
  • Sub cent amounts are economically viable

Software can discover a price, agree to it and pay it inside the same request it was already making.

How it works

Four steps. One round trip.

x402 revives a status code that has been reserved since 1997: 402 Payment Required. X Pay makes it usable in production.

  1. 01

    Request

    A client (a browser, a script or an AI agent) calls a protected endpoint with no payment attached.

    GET /v1/quote
  2. 02

    Quote

    The gateway answers 402 with a machine readable quote: amount, asset, network and recipient.

    402 · X-Payment-Required
  3. 03

    Authorize

    The client signs a payment authorization offchain and retries. No gas, no wallet popup, no block to wait for.

    X-Payment: eyJzaWc…
  4. 04

    Settle

    X Pay verifies the authorization, releases the response immediately, then settles onchain and returns a receipt.

    200 · X-Payment-Response

Why verification and settlement are separate

Waiting for a block confirmation would make every API call as slow as the chain underneath it. X Pay verifies a signed authorization in milliseconds and serves the response straight away, then batches settlement onchain. The merchant carries no chargeback risk, because the authorization is cryptographic and cannot be reversed by the payer.

Products

The full stack, not just a gateway.

Six pieces that turn a single status code into a working business.

X Pay Gateway

The payment engine. Put it in front of any endpoint to price, verify, settle and receipt every call.

  • Per route pricing rules
  • Offchain verify, onchain settle
  • Idempotency and replay protection
  • Webhooks and receipts

Merchant Dashboard

Operations for x402 at the standard the best payment tools set. Publish endpoints, price them, watch revenue land and withdraw it.

  • Create and price APIs
  • Live revenue and call volume
  • Payment and payout history
  • Cohorts, retention, top consumers

AI Wallet

A wallet built for software that spends on its own. Bounded, auditable and revocable by design.

  • Per call and daily spend limits
  • Session keys with expiry
  • Auto pay under a threshold
  • Full transaction history

SDK

One package on each side. Sellers wrap a route, buyers swap fetch for a wallet aware client.

  • Node, Python and Go
  • Express, Fastify and FastAPI adapters
  • Automatic 402 retry
  • Typed receipts

API Marketplace

Publish once and get discovered. Every listing is payable the moment it is found, by humans or agents.

  • Machine readable catalogue
  • Transparent per call pricing
  • Usage and reliability signals
  • Instant, keyless trial

Flexible Billing

Pay per use is the default, not the only option. Mix models per route without changing your code.

  • Per request or per second
  • Token and compute metered
  • Prepaid credits and volume tiers
  • Monthly plans where they fit
Integration

Monetize an endpoint in one line.

Then let any agent pay for it without ever seeing a signup form.

import express from "express";
import { paywall } from "@xpay/sdk";

const app = express();

// price this route, that is the whole integration
app.use("/v1/summarize", paywall({
  price:   "$0.002",
  network: "base",
  payTo:   "0xA1c4…9F2b",
}));

app.post("/v1/summarize", (req, res) => {
  res.json({ summary: summarize(req.body.text) });
});
Marketplace

A catalogue software can shop from.

Every listing carries its price in a format an agent can read, compare and pay, with no onboarding in between.

Search the catalogue
AllAICrypto DataMedia
AI

Text summarization

$0.002 per call
AI

Image generation

$0.040 per image
AI

Translation

$0.0008 per 1k chars
Crypto

Wallet analytics

$0.010 per query
Crypto

Trading signals

$0.250 per signal
Crypto

Onchain data

$0.001 per call
Data

Weather

$0.0002 per call
Media

Speech to text

$0.006 per minute

Illustrative listings and prices, shown to demonstrate the catalogue format.

Token

$XPAY, utility earned by usage.

The network settles in stablecoins. The token exists to align the people who route, secure and grow that traffic.

Fee discounts

Settle protocol fees in $XPAY and pay a reduced rate. The heaviest merchants save the most.

Governance

Vote on fee parameters, supported networks, treasury spend and protocol upgrades.

Staking

Stake to back facilitators and settlement capacity, and earn a share of the fees you help secure.

Ecosystem rewards

Merchant incentives, integration grants and rebates that pay for real volume rather than speculation.

Token design is indicative and subject to change. Nothing on this page is an offer to sell, or a solicitation of an offer to buy, any token or security, and nothing here is investment advice.

Business model

We earn when our merchants do.

One transparent rate on volume, plus optional layers for teams that need more.

1% transaction fee

Charged on settled volume. No monthly minimum, no setup fee, and nothing charged on failed calls.

  • Premium merchant plansHigher limits, priority settlement, advanced analytics and SLAs.
  • Marketplace commissionA share of volume on APIs discovered and sold through the catalogue.
  • Enterprise integrationBespoke deployment, compliance support and dedicated infrastructure.
  • White label gatewayThe full stack running under a partner brand and domain.
  • Cross chain routingA routing fee when a payment settles across networks or assets.
Roadmap

From a gateway to a payment layer.

APIs are the beachhead. The same primitive prices anything a machine can request.

Q3 2026

Gateway and SDK

  • x402 gateway in public beta
  • Node and Python SDKs
  • Merchant dashboard v1
  • Stablecoin settlement on a first EVM network
Q4 2026

Agents and marketplace

  • AI Wallet with session keys and limits
  • API marketplace launch
  • Usage based and prepaid billing
  • Webhooks, receipts and exports
Q1 2027

Scale and token

  • Multichain settlement and routing
  • $XPAY utility and staking live
  • Governance framework
  • Enterprise and white label tiers
Q2 2027 and beyond

Beyond APIs

  • Paywalls for sites, games and media
  • IoT, robotics and DePIN metering
  • Agent to agent settlement rails
  • Fiat on and off ramps
FAQ

Straight answers.

What exactly is x402?

An open standard that puts payment into the HTTP request itself. A server answers an unpaid request with 402 Payment Required and a machine readable quote, then the client attaches a signed payment authorization and retries. X Pay implements that standard and adds the gateway, wallet, dashboard and marketplace around it.

Do my users need a crypto wallet?

Your API consumers need a funded X Pay wallet or any x402 compatible client. For AI agents that means a session key with spending limits. There is no browser extension, no seed phrase prompt and no gas management.

How fast is a payment?

Verification happens offchain in milliseconds, so the response is never held behind a block confirmation. Settlement follows onchain and returns a receipt. Actual latency depends on the network you settle on.

What stops an agent from overspending?

Every session key carries per call and daily ceilings, an expiry, and an optional allowlist of destinations. Limits are enforced before a payment is ever signed, and a key can be revoked instantly.

Can I still charge a monthly subscription?

Yes. Pay per use is the default, but prepaid credits, volume tiers and monthly plans are configurable per route. Most merchants end up mixing them.

Is X Pay live today?

The gateway is in active development, with public beta targeted for Q3 2026. Timelines on this page are plans rather than commitments.

Give your API a price and a payment rail.

Ship pay per use in an afternoon. Let agents buy from you the moment they find you.