// x402_compatible

x402-native.
Out of the box.

When your agent hits an HTTP 402 response, Proco executes the payment automatically — zero extra code, sub-10-second settlement, full audit trail.

Backed by Google Anthropic Visa AWS Cloudflare
How it flows

Four steps. Zero configuration.

Proco listens for 402 responses on your agent's behalf and handles the entire payment cycle — automatically.

STEP 01
→
Agent fires request
GET https://api.example.com
/data/market-feed
STEP 02
⚡
Server returns 402
HTTP 402
{ amount: "0.10",
  currency: "USDC",
  payTo: "0x..." }
STEP 03
🔐
Proco executes
Policy check · PASS
Signing transaction
Broadcasting · Base
STEP 04
✓
HTTP 200 · Access granted
status: settled
time: 8.2s
tx: 0xabc123...
Total developer overhead: 0 lines of code
Developer experience

Before vs. after Proco.

Handling x402 manually means parsing 402 responses, signing transactions, broadcasting, and retrying — on every request. With Proco, it's three lines.

Without Procotypescript
const res = await fetch(url); if (res.status === 402) { const details = await res.json(); const wallet = getWallet(); const tx = await wallet .signTransaction(details); await broadcastTransaction(tx); const receipt = await waitForConfirmation(tx.hash); // check policy violations... // handle retry logic... // write to audit log... const final = await fetch(url, { headers: { 'X-Payment': receipt.hash } }); }
~18 lines · manual policy · no audit log
With Procotypescript
import { Proco } from '@proco/sdk'; const proco = new Proco({ apiKey: 'sk_...', wallet: myWallet }); // Handles 402 automatically: const res = await proco.fetch(url); // Policy checked. Payment executed. // Audit log written. Retried. // res is the 200 response body.
3 lines · policy enforced · full audit trail
Protocol walkthrough

How it works.

x402 is an open standard. Proco implements it fully on the client side — your agent just calls proco.fetch().

01 · Agent
Makes a standard HTTP request
Your agent calls proco.fetch(url) exactly like fetch(). No special headers. No prior payment negotiation.
GET / POST / any method
02 · Server
Responds with HTTP 402
The API returns a standard 402 response with a JSON body containing the amount, currency, and destination wallet. Any x402-compatible server works — no Proco dependency on the server side.
Open standard · server-agnostic
03 · Proco
Executes, settles, retries
Proco evaluates your wallet's policy, signs the transaction, broadcasts to the chain, waits for settlement, writes the audit log, then retries the original request with the payment receipt. Your agent receives the 200 response.
~8s end-to-end · full audit trail
Supported chains

Live today.

x402 payments settle on Base by default. Solana support in beta. Ethereum mainnet coming Q2 2026.

Base · Live
Solana · Beta
Ethereum · Q2 2026
// add_x402

Add x402 to your agent
in 3 lines.

Request early access. Sandbox credentials in 24 hours.

Request early access → View on GitHub →