Payment management
Review payments, balances and transaction history from the merchant workspace.
The payment layer for the autonomous economy.
Connect your business, APIs and AI agents to programmable payments.
Live on Base and BNB Chain.

Payment rails & protocols
X-Pay connects businesses, APIs and AI agents to programmable payments. Integrate payment collection, paid API access and usage billing into your application.
Explore the platform
Businesses · Agents · APIsManage payments, balances and metered usage.
A merchant workspace for your payment operations.
Payment activity and usage at a glance.
Card and crypto payment activity.
Stripe-powered payments, managed through X-Pay.
Stablecoin payments with supported network options.
Card charges clear through Stripe. Onchain settlement is a separate step.
Meter consumption by request, token or time.
Configure billing by request, token or time.
Align charges with how customers use your product.
Review payments, balances and transaction history from the merchant workspace.
Measure consumption and bill by request, token or time.
Use projects, API keys and webhooks to connect payments to your application.
x402 adds payment requirements to HTTP requests. A client receives a price, authorizes payment and retries to access the protected resource.
Your agent calls a
protected resource.
GET /api/researchThe server returns
a payment requirement.
Payment RequiredThe client signs and
retries with payment.
Payment signaturePayment is verified.
The resource is returned.
200 OKUse the JavaScript SDK, REST API and x402 middleware to integrate payments into your application. Review the documentation and validate your workflow in test mode.
Read the documentationimport { xpayMiddleware } from
"@xpay-llc/sdk";
// Put a price on your endpoint.
app.get(
"/api/research",
xpayMiddleware({
price: "0.002",
currency: "USDC",
network: "base",
}),
handler
);
// Your resource. Now payable.
import { XPay } from "@xpay-llc/sdk";
const xpay = new XPay({
apiKey: process.env.XPAY_API_KEY,
});
// Create a card payment.
const payment = await
xpay.payments.create({
amount: "10.00",
currency: "USD",
paymentMethod: "stripe",
});
console.log(payment.id, payment.status);
# Explore available x402 resources.
curl https://www.api-xpay.com/x402
# Inspect the OpenAPI specification.
curl https://www.api-xpay.com/openapi.json
# Call an endpoint without payment.
curl -i https://www.api-xpay.com/x402/ping
# A protected route returns HTTP 402.
# Inspect its payment requirement,
# then use an x402 client to authorize.
# Review the quoted price before paying.Every paid request starts with explicit terms. Your agent reads the amount, asset, network and recipient before it authorizes payment.
Explore paid resourcesHTTP 402
Connect your paid routes to the X-Pay facilitator for payment verification and settlement on Base and BNB Chain.
Sign in to your dashboard, verify your email, and generate a facilitator API key for your project.
Get facilitator API key →Our robotics vision extends programmable payments to machines that earn from completed work and pay for the services they use.
AI is the brain.
Robotics is the body.
X-Pay is the
payment layer.
Machine payment layerX-Pay brings together card and crypto payments, x402-protected APIs and usage billing. The merchant app includes projects, API keys, webhooks, transaction history and wallet settings. Review the documentation for your intended integration.
A protected endpoint responds with HTTP 402 and a machine-readable payment requirement. The client authorizes the payment and retries. The server verifies it and returns the resource. X-Pay’s public catalogue uses USDC on Base.
The platform documents Stripe-powered card payments and crypto payment flows. Card payments clear through Stripe into the X-Pay ledger. Settlement to an onchain wallet is a separate step.
Robotics is a near-term expansion of X-Pay’s payment infrastructure. The focus is on machines that can earn from completed work and pay for the services they use.
The vision includes AI agents paying robots for completed tasks, and robots using their own wallets to buy AI models, APIs, compute, charging and bandwidth. Machines could receive and authorize payments within configured limits, without a person approving every transaction.
Merchants use an account, project and API key to integrate the platform. Buyers calling X-Pay’s public x402 resources use a supported payment client and wallet authorization instead of an API key. Merchant integration and paid API consumption are separate workflows.
Open the merchant app, review the quickstart and validate your integration in test mode. To consume a paid API, browse the public x402 catalogue and inspect its current payment requirements.