Skip to main content
ByteSpike bills in credits, where 1 USD = 1,000,000 credits (micro-USD precision). You buy credits from Console → Billing; they land in the org wallet and any key on the account can spend against them.

​
The flow

  1. Open console.bytespike.ai/billing
  2. Click Top up
  3. Pick an amount (5minimum,5 minimum, 1,250 max per transaction)
  4. Pay via Stripe (cards / Apple Pay / Google Pay)
  5. Credits appear in the wallet within ~30 seconds of payment confirmation — refresh the page if it doesn’t update on its own
You can also subscribe to a tier instead of (or in addition to) ad-hoc top-ups — see Subscriptions below.

​
Bonus ladder

Larger one-time top-ups carry a bonus. Live numbers at bytespike.ai/pricing; the current ladder is roughly:
Top-upBonusCredits delivered
5–5 – 19.990%what you paid
20–20 – 99.99+3%20→20 → 20.60
100–100 – 499.99+5%100→100 → 105
500–500 – 999.99+8%500→500 → 540
1,000–1,000 – 1,250+11.2%1,000→1,000 → 1,112
Bonuses are credited at the same time as the principal — one wallet movement, two line items in the billing-transactions log.

​
Subscription tiers

If you spend more than ~$80/month on the same usage shape, a subscription beats top-ups: bundled credit + higher concurrency + priority queue.
TierCostWhat you get
Free$0Trial allowance for new accounts. All 40+ models, standard rate limits.
Pro¥149/month (~$20)50–500 messages per 12h window. Priority queue. +5% top-up bonus on top of the ladder above.
Max¥1,499/month (~$200)500–5000 messages per 12h. Higher concurrency. +11.2% top-up bonus.
EnterpriseCustom annualUnlimited + SLA, self-hosted option, SSO/OIDC, audit logs. Email enterprise@bytespike.ai.
Manage subscriptions at Console → Subscriptions.

​
Per-key spend caps

Even with a fat org wallet, you can cap individual keys so a runaway loop on one client doesn’t drain the whole wallet:
  • quota (USD) — lifetime spend cap. Set at key creation or edit later. 0 = unlimited (within the wallet).
  • rate_limit_5h / _1d / _7d (USD) — rolling-window caps. Useful for protecting against burst spikes.
  • expires_in_days — auto-revoke for time-bound work.
See Authentication for the full per-key control list, or the Console → API keys edit dialog.

​
Where the credits go

Once topped up, every API call against your keys debits the wallet. You can see the running balance:
  • On every response: X-Quota-Remaining-Credits (key) / X-Org-Quota-Remaining-Credits (org wallet)
  • In the console: Usage
  • Programmatically: /api/v1/me/account — current balance + org context; /api/v1/me/usage — per-call cost log

​
Refunds

ByteSpike does not auto-refund unused credits. They roll forever on the wallet — there’s no monthly expiry. If you need a manual refund (account closure, accidental top-up), email support@bytespike.ai. Refunds go back via the original Stripe charge when possible.

​
Failed top-ups

If the Stripe charge succeeded but credits didn’t land within 5 minutes, check /api/v1/me/billing/transactions — the transaction will show status: "pending" (still processing) or status: "failed" (problem at the payment processor). For failed transactions, the card was usually pre-authorized but not captured — your statement will show the auth dropping off in 24-48h. Persistent issues: email support with the transaction id from that endpoint.

​
Next

Register

Step before this one.

Configure your client

Spend the credits.

Pricing reference

Per-model rates inside the docs.

Credits & billing concept

The deeper mental model.