Pricing

Pay-per-call, frozen at purchase. Configure a baton, price it live against the API, and copy the curl to create it.

Calculator

We charge a network minimum of $0.001 on every order — one-tenth of a cent. Not because we want to, but because it's about the smallest amount we can settle on-chain once gas costs are covered. As micro-transaction payment options improve, we'll find a way to lower it. In the meantime, please enjoy one of the few places on the internet where a penny keeps you productive all day.

Pricing

Baton is pay-per-call. You pay for each baton you create and each operation you run — no subscription, no monthly minimum, no commitment. Use it once and you are billed once; never use it again and you are billed nothing. Every billable order is charged at least a small network minimum (a fraction of a cent).

A baton’s price is resolved at creation and frozen for its life; later pricing changes never touch an already-issued baton.

What drives the price

Two real costs: storage (size × time) and egress (data read back out). Write counts and metadata lookups cost something too, but they are dwarfed by storage and egress and are absorbed into the margin on those. The trust layer — document-witness and hash-chaining — is priced separately as prepaid flags.

Configuring a baton — every baton is the same handful of choices: a write behavior, how much it holds (size, duration, egress), how it is shared (tokens and their caps), what happens at end of life, and whether it carries a document-witness. Start from a use case or set every option yourself; the calculator above prices what you configure, live.

Three ways to pay

Pay per call with x402 — sign an EIP-3009 authorization (USDC or EURC) off-chain, attach it as an X-Payment header, send the call. No account, no signup, no balance to manage. The wallet that signs is your identity for any later history reads.
Pre-funded balance via Stripe — sign in with Google or GitHub, top up via Stripe, mint an rs_live_* key. Calls draw down the balance. No recurring charges.
Wallet JWT — sign in via EIP-191 personal_sign, get a short-lived token, then authorize balance-based debits like the API-key path.

All three resolve to the same customer identity and ledger; you can move between them without losing history.

Currency and refunds

All prices are USD-denominated. The on-chain settlement assets for x402 are USDC or EURC (Base Sepolia for v1); on-chain transfers carry no separate facilitator fee. Terminal-failure refunds run through the same billing layer that takes the charge — x402 customers get the same asset back to the signing wallet; balance customers get a credit.