Billing

SolidPeer bills in Compute Credits (CC). Each request costs some number of CC; your account starts each cycle with a grant of CC and is exhausted when the balance hits zero.

How charging works

Every request goes through three steps:

1. Reservation — the gateway estimates the call's cost and holds that many CC against your balance. If the reservation exceeds your balance, the request returns 429 insufficient_balance before reaching the upstream.
2. Execution — the gateway forwards your request to the appropriate node.
3. Commit — the gateway reconciles the reservation against the actual cost (which can be cheaper if the response was small, or pricier if you hit a write-method surcharge).

Cache hits charge the same as cache misses — caching is a server-side optimization, not a discount.

What costs how much

Costs depend on the method called and the network it's on. See /pricing for current per-system rates.

Per-network multiplier applies on top of the per-method cost:

• mainnet → 1×
• chipnet, testnet4, regtest → 0.5×

Account states

Your account is always in one of three states:

• active — has balance, requests pass.
• suspended — operator-flagged. Requests return 403 account_suspended. Contact us if this happens unexpectedly.
• expired — subscription cycle ended without renewal. Requests return 403 account_expired. Renew via the dashboard to restore service.

Cycle renewal

Each paid tier runs in cycles (30 days for monthly, 365 days for annual). Cycle start grants the tier's CC quota. Cycle end:

• If renewed: prior cycle's unused CC stays on the account; the new cycle's grant is added on top.
• If not renewed: account flips to expired. Your data and tokens are preserved for 30 days, then reaped.

The dashboard sends notifications at 90% CC use, at 100% CC use, and at 7 days / 1 day before cycle expiry. Configure delivery (email / Telegram / browser push) under Notifications.

Top-ups

If your balance runs low mid-cycle, top up without changing tier — the dashboard takes a one-off BCH or CashToken payment and credits the resulting CC. Top-up rate matches your tier's $/M-CC rate. Minimum top-up is $5.

No overage, no auto-charge

Crypto billing rules out card-on-file auto-charging. Once your balance hits zero, requests reject with 429 insufficient_balance until you top up, upgrade, or the cycle renews. There's no automatic overage; you control when money leaves your wallet.

Tier downgrades

Schedule a downgrade from the dashboard. The change takes effect at the end of the current cycle; the prior tier's caps and grant remain in force until then.

Token-level budgets

You can mint a token with its own one-time CC budget (Build tier and above). Once the token has spent that many CC, it returns 429 token_budget_exceeded — independent of your account balance. Useful for capped contractor credentials.