Top-up runbook
Packs settle in USDC.
POST /api/v1/checkout/x402 accepts topup-1000 or topup-3000, settles the pack price in USDC, and grants credits immediately with idempotency on the settlement transaction hash. Humans can still buy the same packs through Stripe.
- Packs
- Same SKUs
- Idempotency
- Tx hash
- MCP tools
- No card tool
Fund the ledger from the CLI
Follow the sequence in order. Each step is a bounded operator action—not a promise that every deployment has x402 enabled.
- 01
List current packs
Run npx @offlinecreator/mcp topups to read the live pack IDs, credits, and USD prices before purchasing.
- 02
Top up with wallet
With X402_EVM_PRIVATE_KEY set, run topup --id topup-1000 or topup-3000. The client pays over x402 when the server rail is enabled.
- 03
Force Stripe when needed
Pass --stripe to always create a human Checkout URL, or rely on automatic fallback when the server reports x402 unavailable.
- 04
Verify the grant
Run balance after settlement or after the human completes Checkout. Do not start generation until the new balance is observed.
- PacksSame SKUs
x402 sells the same top-up IDs and credit amounts published for Stripe.
- IdempotencyTx hash
Credit grants key on the settlement transaction so retries cannot double-credit.
- MCP toolsNo card tool
Top-up remains CLI/API. MCP agents report shortfalls; they do not complete Stripe Checkout.
Runbook FAQ
Which pack IDs are valid?
topup-1000 and topup-3000. Confirm live credits and USD amounts with the topups command or the pricing page before purchase.
Does MCP expose a top-up tool?
No. Discovery and purchase stay on CLI/API so card checkout cannot hide inside an MCP tool call. Wallet settlement is a local client capability around those HTTP routes.
Keep payment decisions explicit.
Humans stay on Stripe. Agents settle only with a local wallet and a spend cap. When the shape is unclear, start with the PAYMENT-REQUIRED diagnosis runbook.