Your agent has a wallet now. Here's something worth buying.

Quickstart: first paid call in ~20 lines

Install the SDK and the x402 packages it builds on:

npm install @coinbase/cdp-sdk @x402/core @x402/evm @x402/svm @x402/extensions @x402/fetch

Set CDP_API_KEY_ID, CDP_API_KEY_SECRET, and CDP_WALLET_SECRET from the CDP Portal. The client provisions a managed wallet on first use — no private keys to store.

import { CdpX402Client } from "@coinbase/cdp-sdk/x402";
import { wrapFetchWithPayment } from "@x402/fetch";

const client = new CdpX402Client();

// Fund this address with a little USDC on Base before the first payment:
const { evmAddress } = await client.getAddresses();
console.log("fund me:", evmAddress);

const payingFetch = wrapFetchWithPayment(fetch, client);

// $0.015 — honeypot / rug-risk scan for any EVM token
const res = await payingFetch(
  "https://onchainpulse.theaslangroupllc.com/api/evmtoken?address=0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984&chain=base"
);
console.log(await res.json());

That's the whole flow: the endpoint answers with an HTTP 402 quote, the SDK signs a USDC payment authorization with the managed wallet, replays the request, and the data comes back. Settlement runs through the CDP facilitator — the same infrastructure PulseNetwork has settled on since launch.

Spend controls, verified against a live endpoint

Caps are enforced client-side before any funds move. A cap below the endpoint's price throws SpendControlError (per_payment_cap) instead of paying; within caps, the payment settles normally. Both behaviors were tested against the endpoint above on 2026-07-23. Amounts are atomic USDC units (6 decimals — 15000n = $0.015).

const USDC_BASE = "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913";

const client = new CdpX402Client({
  spendControls: {
    maxAmountPerPayment:     { atomic: 50_000n,  asset: USDC_BASE }, // ≤ $0.05 per call
    maxCumulativeSpend:      { atomic: 1_000_000n, asset: USDC_BASE }, // ≤ $1.00 …
    maxCumulativeSpendWindow: "24h",                                   // … per day
  },
});

Usage-based pricing (upto scheme) — six live endpoints

The SDK's other launch feature is the upto scheme: your agent authorizes a maximum, the seller settles only what the request actually used. Six PulseNetwork endpoints run it in production — every one verified on-chain with a CDP managed wallet. CdpX402Client supports upto on Base out of the box, and the one-time Permit2 allowance is gas-sponsored — a fresh managed wallet with zero ETH pays with no setup. Exact-scheme payments still work everywhere at the flat price.

• longevitypulse…/api/longevity/clinical-trials?max_trials= — $0.04 + $0.003/trial (1–20, authorize $0.10)
• govspendpulse…/api/govspend/us-contracts?limit= — $0.03 + $0.0025/award (1–20, authorize $0.08)
• govspendpulse…/api/govspend/eu-tenders?limit= — $0.03 + $0.0025/notice (1–20, authorize $0.08)
• truthpulse…/api/truth/new-releases?limit= — $0.03 + $0.0025/release (1–20, authorize $0.08)
• footballpulse…/api/accumulator?max_legs= — $0.07 + $0.01/leg (2–8, authorize $0.15)
• edupulse…/api/exam/flashcards?count= — $0.20 + $0.015/card (1–20, authorize $0.50)

// authorize up to $0.10, settle $0.049 for 3 trials — same payingFetch as above
const res = await payingFetch(
  "https://longevitypulse.theaslangroupllc.com/api/longevity/clinical-trials?condition=rapamycin&max_trials=3"
);