Pricing.
One $/CC schedule per customer — top-ups happen at your tier rate, no separate overage line. Heavy use prompts a tier upgrade naturally. Headline floor: from $0.02 per million credits at the Scale tier.
hobby
or annual at ~17 % off (10× monthly)
Entry tier — accessible enough for any working developer to keep around as a backup endpoint.
- Credits: 300M CC / mo
- RPS: 25 sustained, 500 burst
- Tokens: 3
- Subs: 25
build
or annual at ~17 % off (10× monthly)
Production small-app workloads. Per-token method scope and RPS caps for browser-deployed credentials.
- Credits: 1.3B CC / mo
- RPS: 75 sustained, 1500 burst
- Tokens: 10
- Subs: 100
scale
or annual at ~17 % off (10× monthly)
Volume sweet spot. Per-token sub-budgets, webhooks on lifecycle events, prioritized support.
- Credits: 9.5B CC / mo
- RPS: 200 sustained, 4000 burst
- Tokens: 25
- Subs: 500
business
or annual at ~17 % off (10× monthly)
Commit volume + tighter SLA + dedicated capacity hints. Pays for the features more than the credits.
- Credits: 20B CC / mo
- RPS: 500 sustained, 10000 burst
- Tokens: 50
- Subs: 2500
Estimate your bill.
Plug in your expected monthly call volume and average cost per call. We pick the smallest tier that covers it; everything beyond the tier quota bills at the same $/M rate (no separate overage table).
- Monthly CC needed
- 250M
- Tier quota (hobby)
- 300M
- Monthly base
- $9.99
- Effective monthly cost
- $9.99
- Effective $/M CC
- $0.0400
These numbers use the public per-method weights. Your actual mix may differ — the per-call CC charge varies by method. See /methods for the full table.
Dedicated
Reserved capacity, custom CC grants, contracted SLA. Top-up floor $0.0200 per million credits — matches the Scale published rate so the negotiation can't race below the volume tier. Multi-region available on request.
What's in each tier.
| hobby | build | scale | business | |
|---|---|---|---|---|
| Monthly Compute Credits | 300M | 1.3B | 9.5B | 20B |
| Effective $/M CC | $0.0333 | $0.0308 | $0.0211 | $0.0300 |
| RPS (sustained) | 25 | 75 | 200 | 500 |
| RPS burst | 500 | 1500 | 4000 | 10000 |
| Active tokens | 3 | 10 | 25 | 50 |
| Concurrent subscriptions | 25 | 100 | 500 | 2500 |
| Per-token method scope | — | ✓ | ✓ | ✓ |
| Per-token RPS cap | — | ✓ | ✓ | ✓ |
| Per-token sub budgets | — | — | ✓ | ✓ |
| Webhook on events | — | — | ✓ | ✓ |
| Support response | 48h | 24h | 12h | 4h |
| Dedicated capacity hint | — | — | — | ✓ |
Mid-cycle top-ups.
Out of credits before cycle end? Buy more at your current tier rate. Same $/CC schedule you signed up at — heavy use just rewards a tier upgrade naturally. Minimum $5 USD equivalent so on-chain payment friction stays below the credit value.
Testnet + regtest.
chipnet / testnet4 / regtest requests are billed at half the mainnet CC rate per method. Smaller chains, lower load, real cost recovery — without the fragile "free testnet" framing that breaks under any actual integration-test workload.
FAQ.
No free trial? +
No. Hobby at $9.99/mo is genuinely the cheapest committed-product entry on the market — you can prove the integration works against your real workload for less than a takeout lunch. Pay the first cycle, throw it away if it doesn't fit; we'd rather you commit a $9.99 sanity check than chase a freemium funnel that nobody respects.
What does a Compute Credit actually cost me per RPC call? +
The cheapest method costs 100 CC. A typical wallet-mix workload averages 200-500 CC per call. At Scale's $0.0211/M, that's ~$0.0042-$0.0106 per typical call. Per-method weights are listed at /methods.
Why crypto-only billing? +
No card vault, no chargeback theatre, lower payment-processor cost passed back as cheaper credits. Pay in BCH directly or via PUSD / MUSD stablecoins on CashTokens.
What happens at zero balance? +
429 with a clear `rejected:balance` reason — top up, upgrade, or wait for renewal. No autodebit; the operator never holds your card.
Can I rotate tokens? +
Yes — POST /token mints, POST /token/:id/revoke flips. Multiple active tokens per account; per-token method/origin/RPS caps for browser-deployed credentials.
What if I lose the privkey? +
The account is gone — the privkey IS the recovery secret, stored in your browser as WIF. Back it up to paper; the dashboard nags you about this until you confirm.