Wallets & networks

To use PDF As You Go your client needs a wallet that can sign x402 payments and holds enough USDC to cover the operations you run. There is nothing else to set up — no account, no API key, no prepaid balance.

Token

• USDC (a USD-pegged stablecoin) is the payment token during preview.
• USDC has 6 decimals, so amounts are quoted in base units: $0.05 = 50000 base units. This is the maxAmountRequired value you’ll see in the 402 body.

Price	USDC	Base units
One operation	0.05	50000
Ten operations	0.50	500000

Note

EURC and other ERC-20 tokens are feasible under the same x402 schemes (EIP-3009 / Permit2) and are tracked on the Roadmap. USDC is the only token guaranteed during preview.

Network

Base is the default and recommended network during preview. It offers low fees and is the natural home for USDC.

The USDC contract on Base is:

0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

The x402 ecosystem and its facilitators support additional networks (Polygon, Arbitrum, World, and Solana among them). PDF As You Go advertises the networks it currently accepts in the 402 payment-requirements body — read network and asset from there rather than hard-coding a chain, so your client stays correct as support expands.

Preview

During private preview, plan on Base + USDC. Other networks may be enabled later; the accepts array in the 402 response is always the source of truth for what’s accepted right now.

Funding and costs

• Per operation: $0.05 in USDC.
• Onchain settlement: roughly $0.0001 per payment, paid as part of the transfer. There is no separate platform fee.
• Gas: payments use gasless authorizations (EIP-3009 transferWithAuthorization for USDC), so your wallet does not need the chain’s native gas token just to pay. The facilitator submits the settlement transaction.

Keep enough USDC in the wallet to cover your expected volume. Because each call is metered and priced up front, you can cap spend in your client (for example, a per-session or per-task budget) rather than relying on a plan limit.

Security of the wallet

The wallet key your client signs with is sensitive — anyone holding it can spend its funds. Treat it like any production secret:

• Load it from an environment variable or secret manager, never from source control.
• Prefer a dedicated, low-balance wallet for agent spending rather than a primary treasury wallet.
• Top it up as needed instead of holding a large balance.

See also

• x402 payments — how a payment is constructed and settled.
• The 402 flow — the exact fields, including network and asset.