Credits & payments

One purse. Every cost.
One receipt.

A single balance covers everything an action spends — compute, model tokens, egress, and paid upstream vendors. You see an estimate before, you never pay above its ceiling, and the receipt after itemizes every line.

The purse

One balance, inside and out.

Your credits pay for the platform's own work — compute, model passes, bytes moved — and for what actions spend upstream: the platform treasury fronts vendor micropayments and settles them against your receipt.

Per-destination sub-caps ride inside every authorization, so no single upstream can drain what you approved. Only curated vendors are ever paid →

Where balance comes from

  • A free monthly allowance — every identity gets one, no account needed.
  • Card top-ups when signed in — the packages below.
  • Agents can skip the balance entirely and pay per cast over x402. The agent surface →
Estimates

Ceilings, not guesses.

Before an action runs you see three numbers, not one. They are computed from real receipts and upstream quotes — and the third one is a hard limit, not a forecast.

Typical

The p50 — what half of real runs actually cost. Your best guess at the bill.

p95

What all but the largest runs stay under. A long selection or a busy upstream lands here.

Ceiling

The most this run may spend, reserved up front. Spend stops here — and whatever was reserved but not spent refunds, every time.

An estimate is never a fixed price, and a price on this site is never a promise — the ceiling is the promise. You authorize the ceiling; the run spends at most that; the remainder comes back.

Receipts

Every line, and the lines sum.

Every run returns a signed, itemized receipt. A worked example — the shape, not today's prices:

LineWhat it isCredits
Computewasm fuel the steps burned0.2
Model tokensthe streaming llm pass6.9
Egressbytes fetched from allowlisted hosts0.4
Upstream vendorhost-priced: the vendor's real charge, with its payment proof2.0
Developer-priced callthe author's own price on one call, max declared up front2.0
Developer feethe author's declared margin0.5
Totalthe lines sum to this — on every receipt, by construction12.0
Reserved ceilingauthorized before the run18.0
Refundedceiling − total, back to your balance6.0

Receipts are signed (ed25519), state which evidence they carry, and pin the exact rates they settled under — a later rate change never re-prices a past run. A public verifier checks the signature and the arithmetic.

Units & rates

Three units, one table.

Pixie is the meter's exact unit — what the sandbox counts in. Credits are what you hold and see. Settlement currency is what a card or an x402 rail moves. One published table converts between all three, and every receipt pins the rows it settled under.

ResourceUnitCredits
Buying credits

Free to start. Card to top up.

Wandlet works with no account: free credits to try it, and an account when you want card billing or teams.

Free allowance

Every identity — signed in or not — gets a monthly credit allowance sized for about five actions a day. It spends through the same credits economy as everything else; there is no separate quota.

Card, signed in

Sign in to top up by card — the packages below. Bought credits land in the same balance the allowance tops up.

Wandlet does not take USDC for credits. A balance is funded by the allowance and by card, and no Wandlet surface issues an address for receiving USDC. Agents paying per cast over x402 settle in USDC on their own rail — that path never funds a balance.

Buy credits from your account Pricing on the home page