x402-payments

Category: Tools & Productivity | Uploader: valeo-cash | Downloads: 0 | Version: v1.0（Latest）
Use whenever the user wants to add payments to an API, monetize endpoints, implement x402, handle HTTP 402 responses, create paid APIs, set up crypto paywalls, accept USDC, or build agent payments. Trigger on: x402, 402 Payment Required, paid API, paywall, micropayments, USDC payments, agent payments, monetize API, payment middleware, x402-next, x402-express, x402-fetch, Sentinel, payment router, audit trail, budget caps, payment receipts, facilitator. Also trigger when turning a free API into paid, adding per-request pricing, or building AI agent autonomous payment flows. Covers Base (EVM), Solana, and Stellar with USDC.
Changelog: Source: GitHub https://github.com/valeo-cash/x402-payments-skill
Directory Structure

Current level: x402-payments/
📁 references/
- 📄 base-evm.md 7.3 KB
- 📄 packages.md 6.7 KB
- 📄 sentinel-router.md 10.5 KB
- 📄 solana.md 7.2 KB
- 📄 stellar.md 19.9 KB
📄 SKILL.md 11.2 KB
SKILL.md

---
name: x402-payments
description: >
  Use whenever the user wants to add payments to an API, monetize endpoints, implement x402,
  handle HTTP 402 responses, create paid APIs, set up crypto paywalls, accept USDC, or build
  agent payments. Trigger on: x402, 402 Payment Required, paid API, paywall, micropayments,
  USDC payments, agent payments, monetize API, payment middleware, x402-next, x402-express,
  x402-fetch, Sentinel, payment router, audit trail, budget caps, payment receipts, facilitator.
  Also trigger when turning a free API into paid, adding per-request pricing, or building
  AI agent autonomous payment flows.   Covers Base (EVM), Solana, and Stellar with USDC.
  Trigger on: Stellar, Soroban, Freighter, OpenZeppelin, OZ Channels, auth-entry, SEP-41, fee bump, smart accounts, fee-free.
  Even without "x402" mentioned — if they want to charge for API access with crypto or
  build agent payment infrastructure, this skill applies.
---

# x402 Payments

Build paid APIs and agent payment infrastructure using the x402 protocol. Deploy on **Base (EVM)**, **Solana**, and/or **Stellar** with USDC. Optionally add **Sentinel Payment Router** for multi-endpoint orchestration, budget caps, and cryptographic audit trails.

## How x402 Works

x402 is an open payment protocol (by Coinbase) built on the HTTP 402 status code. Any API can charge per-request in USDC — no API keys, no subscriptions, no accounts. Clients (humans or AI agents) pay at the moment of use, and the server verifies payment before granting access.

```
Client → GET /api/data → Server
Client ← 402 Payment Required (pricing in headers) ← Server
Client → GET /api/data + X-PAYMENT header (signed authorization) → Server
Server → verifies via Facilitator → settles USDC on-chain
Client ← 200 OK (data) ← Server
```

## Decision Tree

When a user asks for x402 help, determine three things:

### 1. Role: Seller or Buyer?

- **Seller** (API provider) — wants to charge money for their endpoints → Server setup
- **Buyer** (API consumer) — wants to call paid endpoints → Client setup
- **Both** — building a system that both serves and consumes paid APIs

### 2. Chain: Base, Solana, Stellar, or multiple?

- **Base (EVM)** — most common, ~98% of x402 volume uses USDC on Base
  → Read `references/base-evm.md`
- **Solana** — growing ecosystem, uses SPL USDC
  → Read `references/solana.md`
- **Stellar** — Soroban smart contracts, auth-entry signing, fee-free via OZ Channels facilitator, under 5s settlement
  → Read `references/stellar.md`
- **Both / all three** — V2 packages support multi-chain registration
  → Read the relevant reference files

### 3. Scale: Single endpoint or multi-endpoint orchestration?

- **Simple** (1-3 endpoints, no audit needs) — basic x402 is sufficient
- **Complex** (multiple endpoints, budget caps, audit trails, AI agents making autonomous payments)
  → Add Sentinel Payment Router. Read `references/sentinel-router.md`

## Quick Reference: All Packages

Read `references/packages.md` for the complete package matrix covering V1 (simple) and V2 (modular) packages, with install commands and compatibility notes.

## Quick Start: Seller on Base (Most Common Path)

This is the fastest path — monetize a Next.js API route on Base mainnet:

```bash
npm install x402-next
```

```typescript
// middleware.ts
import { paymentMiddleware } from "x402-next";

export const middleware = paymentMiddleware(
  "0xYourWalletAddress",
  {
    "/api/premium": {
      price: "$0.01",
      network: "base",
      config: { description: "Premium API access" },
    },
  },
  { url: "https://x402.org/facilitator" }
);

export const config = {
  matcher: ["/api/premium/:path*"],
};
```

```typescript
// app/api/premium/route.ts
import { NextResponse } from "next/server";

export async function GET() {
  return NextResponse.json({
    data: "This endpoint costs $0.01 per call",
    timestamp: Date.now(),
  });
}
```

Deploy to Vercel. Any request without payment gets a 402 with pricing. Clients with valid X-PAYMENT headers get data.

## Quick Start: Seller on Stellar

Stellar-only, fee-free for clients (facilitator covers fees). Use the OZ Channels facilitator:

```bash
npm install @x402/express @x402/core express
```

```typescript
import express from "express";
import { paymentMiddleware } from "@x402/express";

const app = express();

app.use(
  paymentMiddleware(
    {
      "GET /weather": {
        accepts: [
          {
            scheme: "exact",
            price: "$0.001",
            network: "stellar:testnet",
            payTo: process.env.STELLAR_PAY_TO_ADDRESS!,
          },
        ],
        description: "Weather report",
      },
    },
    {
      url: "https://channels.openzeppelin.com/x402/testnet",
      headers: process.env.OZ_RELAYER_API_KEY
        ? { "x-api-key": process.env.OZ_RELAYER_API_KEY }
        : undefined,
    }
  )
);

app.get("/weather", (_req, res) => {
  res.json({ city: "London", temperature: 22, conditions: "Partly cloudy", timestamp: Date.now() });
});

app.listen(3000);
```

Set `STELLAR_PAY_TO_ADDRESS` (your G... address) and optionally `OZ_RELAYER_API_KEY`. Clients sign auth entries (e.g. with Freighter); no XLM needed.

## Quick Start: Buyer on Base

```bash
npm install x402-fetch viem
```

```typescript
import { wrapFetchWithPayment } from "x402-fetch";
import { createWalletClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { base } from "viem/chains";

const account = privateKeyToAccount(process.env.PRIVATE_KEY as `0x${string}`);
const wallet = createWalletClient({ account, chain: base, transport: http() });
const paidFetch = wrapFetchWithPayment(wallet);

const response = await paidFetch("https://example.com/api/premium");
const data = await response.json();
```

## Quick Start: Multi-Endpoint with Sentinel Router

```bash
npm install @x402sentinel/router
```

```typescript
import { PaymentRouter } from "@x402sentinel/router";

const router = new PaymentRouter({
  paymentFetch: paidFetch,
  getPaymentInfo: () => null,
  agentId: "my-agent",
  apiKey: "sk_...",
});

const result = await router.execute({
  name: "research-pipeline",
  maxBudgetUsd: "0.05",
  strategy: "parallel",
  endpoints: [
    { label: "email-verify", url: "https://api.example.com/verify?email=test@gmail.com" },
    { label: "dns-lookup",   url: "https://api.example.com/dns?domain=google.com" },
    { label: "ssl-check",    url: "https://api.example.com/ssl?domain=google.com" },
  ],
});

// result.receipt — unified SHA-256 receipt linking all payments
// result.receipt.receiptHash — tamper-proof hash
// result.receipt.sentinelSig — HMAC server signature
```

Read `references/sentinel-router.md` for the full Router API.

## Mainnet vs Testnet

| | Testnet | Mainnet |
|---|---------|---------|
| **Base** | `base-sepolia` / `eip155:84532` | `base` / `eip155:8453` |
| **Solana** | `solana-devnet` | `solana-mainnet` |
| **Stellar** | `stellar:testnet` | `stellar:pubnet` |
| **Facilitator** | `https://x402.org/facilitator` | `https://x402.org/facilitator` |
| **Stellar Facilitator** | `https://channels.openzeppelin.com/x402/testnet` | Coming soon |
| **Token** | Testnet USDC (free from faucets) | Real USDC |

Always start on testnet. Switch to mainnet by changing the network string.

## Key Concepts

- **Facilitator**: Verifies and settles payments on-chain. Public one at `x402.org/facilitator` is free. Stellar uses OZ Channels.
- **Scheme**: Payment structure. `exact` = fixed price per request.
- **EIP-3009**: Token standard enabling gasless USDC transfers. Why x402 works primarily with USDC.
- **CAIP-2**: Chain identifier format. `eip155:8453` = Base. `solana:5eykt...` = Solana mainnet. `stellar:pubnet` / `stellar:testnet` = Stellar.
- **Soroban Authorization**: Stellar's smart contract auth model. Clients sign auth entries with `max_ledger` expiration bounds instead of full transactions. Lighter than Solana's transaction signing.
- **SEP-41**: Stellar's token interface standard. Covers both classic Stellar assets and Soroban contract tokens. USDC, PYUSD, and USDY on Stellar implement SEP-41.
- **Fee-Free Settlement**: On Stellar, the OZ Channels facilitator covers all network fees. Clients don't need XLM. Transaction costs are ~$0.00001.
- **Smart Accounts**: OpenZeppelin smart account contracts on Stellar with spending limits, multisig, and scoped permissions. The budget/guardrail layer for autonomous agents.

## Common Patterns

### Multiple routes with different prices
```typescript
export const middleware = paymentMiddleware(
  "0xYourAddress",
  {
    "/api/basic":   { price: "$0.001", network: "base" },
    "/api/premium": { price: "$0.01",  network: "base" },
    "/api/bulk":    { price: "$0.10",  network: "base" },
  },
  facilitator
);
```

### Accept payments on Base, Solana, and Stellar (V2 — two facilitators)

Base and Solana use x402.org; Stellar uses OZ Channels. Configure both.

```typescript
import { paymentProxy, x402ResourceServer } from "@x402/next";
import { HTTPFacilitatorClient } from "@x402/core/server";
import { ExactEvmScheme } from "@x402/evm/exact/server";
import { ExactSvmScheme } from "@x402/svm/exact/server";

const x402Facilitator = new HTTPFacilitatorClient({ url: "https://x402.org/facilitator" });
const server = new x402ResourceServer(x402Facilitator)
  .register("eip155:8453", new ExactEvmScheme())
  .register("solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp", new ExactSvmScheme());

export const middleware = paymentProxy({
  "/api/data": {
    accepts: [
      { scheme: "exact", price: "$0.01", network: "eip155:8453", payTo: "0xEvmAddress" },
      { scheme: "exact", price: "$0.01", network: "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp", payTo: "SolanaAddress" },
      { scheme: "exact", price: "$0.01", network: "stellar:testnet", payTo: process.env.STELLAR_PAY_TO_ADDRESS! },
    ],
    description: "Multi-chain premium data",
  },
}, server);
```

Stellar routes require the OZ Channels facilitator (separate client); see `references/stellar.md` for full tri-chain setup with both facilitators.

## Troubleshooting

| Problem | Fix |
|---------|-----|
| 402 but no payment details | Check middleware matcher covers the route |
| "facilitator unreachable" | Verify `https://x402.org/facilitator` is accessible |
| Payment succeeds but 401 | Increase `maxTimeoutSeconds` |
| "EIP-3009 not supported" | Use USDC only |
| Solana tx fails | Check SOL balance for rent + USDC balance for payment |
| V1 vs V2 confusion | V1: `x402-next`. V2: `@x402/next`. Don't mix them |
| Stellar: "auth entry expired" | Increase `max_ledger` bounds in auth entry |
| Stellar: "wallet doesn't support signAuthEntry" | Use Freighter browser extension (not mobile) |
| Stellar: facilitator 401 | Check `OZ_RELAYER_API_KEY` is set and valid |
| Stellar: "unsupported network" | Use CAIP-2 format: `stellar:pubnet` or `stellar:testnet` |
| Stellar: need XLM? | No — facilitator covers all fees. Client needs zero XLM. |

## Reference Files

- `references/base-evm.md` — Complete Base/EVM setup (V1 + V2)
- `references/solana.md` — Complete Solana setup
- `references/stellar.md` — Complete Stellar setup (Soroban, Freighter, OZ Channels, Smart Accounts)
- `references/sentinel-router.md` — Payment Router API
- `references/packages.md` — All npm packages
Comments 0
Latest | Hot
Please login before commenting.
No comments yet. Be the first one!
x402-payments

Directory Structure

SKILL.md

Report

Notice
