How to pay with USDC on Base
The kit costs 29 USDC. Send a round 29 from your wallet, sign one free message, download. The network fee on Base is usually a few cents.
From a wallet (recommended)
- Send 29 USDC (or more) on the Base network to:0x8ca7ae7A69312a37a11bDA85b8D13b79e9De944eAny wallet works (Coinbase Wallet, MetaMask, Rabby, Rainbow…). Keep a few cents of ETH on Base for the fee, unless your wallet covers it.
- Paste the transaction hash at checkout and select “Verify with my wallet and download”.
- Sign the message your wallet shows. It’s free and moves no money; it proves you’re the one who paid. The download starts straight away.
Shortcut: open this site in your wallet’s browser (or with a browser-extension wallet) and press “Pay 29 USDC with my browser wallet”. It pays, asks for the signature and downloads in one go. Wallet can’t connect to the page? Use “Sign by hand” at checkout and paste the signature.
From an exchange
Exchanges (Coinbase, Binance, Kraken…) send from their own wallets, so they can’t sign for you. At checkout open “Paying from an exchange?”, get an order code and an amount with cents such as 29.37, and withdraw exactly that on Base within 2 hours. The store must receive the exact amount: if the exchange takes its fee out, add it on top. Then paste the hash next to your order code. Or withdraw to your own wallet first and use the wallet path.
Paying from an AI agent or x402 client
The problem: an agent built from the official x402 quickstart can’t buy this kit through GET /download. Its client library, @x402/core, caps each payment at $1 by default (DEFAULT_MAX_AMOUNT_PER_PAYMENT, source). When we pointed a default @x402/fetch 2.28.0 client at this $29 endpoint on 19 October 2026, it got the 402 and threw before signing anything: rejected by spendControls.maxAmountPerPayment ($1, including USDC). Nothing is charged, but the agent gets an error instead of the file.
Raising the cap isn’t enough here. This store doesn’t settle signed x402 payments through a facilitator. A client with a higher cap will sign and retry, and the store answers with another 402 that points to the direct-payment path. The store doesn’t submit the signed authorization, so that retry charges nothing either.
What works: the agent sends 29 USDC on Base from a wallet it controls, signs the text from GET /claim/message?txHash=… and calls POST /claim with {"txHash","signature"} (details in llms.txt). A person can follow the wallet steps above. How x402 clients pay in general, including how to set that cap: How does an AI agent pay an x402 endpoint?
If something goes wrong
Sent the wrong amount, paid from an exchange without an order, or stuck? Email soloearn@agentmail.to with the transaction hash (and order code if you have one) and we’ll sort it out with you.
Why sign a message?
Every Base transaction is public, so a hash on its own doesn’t prove you paid: anyone could copy it. Only the wallet that sent the money can produce the signature, so nobody else can claim your download. The kit gives your buyers the same checkout.