RunarsRunars Docs

Billing & auto-reload

Credit model, top-ups, and auto-reload

Runars uses a prepaid credit model. This page covers the credit mechanics and auto-reload, which keeps your balance from running out mid-traffic. For per-model rates and rate limits, see Pricing.

Credit model

  • Prepaid: You prepay for credits, deducted as you make requests.
  • Organization-scoped: Credits belong to an organization, shared by everyone in it.
  • No overage: Requests are rejected with 402 payment_required once the balance hits zero—no surprise bills.
  • Per-request: Each request is debited for its exact token usage at the model's rates.

Manual top-ups

  1. Go to Dashboard → Billing
  2. Click Add Funds
  3. Choose an amount ($5–$500)
  4. Complete the Helcim-powered checkout
  5. Credits are applied immediately and a receipt is emailed via Resend

Auto-reload

Auto-reload automatically charges your saved card to top up your balance whenever it drops to or below a threshold you set. It's ideal for production traffic where a drained balance would mean failed requests.

Configure it under Dashboard → Billing → Auto-reload:

FieldDescription
EnabledMaster toggle.
ThresholdReload whenever the balance falls at or below this amount (e.g. $5).
AmountHow much to charge on each reload (e.g. $20).
Payment methodThe vaulted card to charge.

How it works

  1. After every request, Runars checks whether the balance is at or below your threshold.
  2. If so, it enqueues a single reload for the configured amount against your vaulted card (idempotent—only one reload runs at a time per organization).
  3. On success, your balance is credited and a confirmation email is sent to the org's owners/admins.
  4. On failure, a retry is attempted; if it fails repeatedly, auto-reload is disabled and a notification is sent.

Notifications

Runars sends email notifications (via Resend) for:

  • Low balance — once per day when your balance crosses the threshold and auto-reload is off.
  • Auto-reload success — when a reload charge succeeds.
  • Auto-reload failed / disabled — when a charge fails or auto-reload is disabled after repeated failures.

Notifications are deduplicated so you won't be spammed—for example, a low-balance email is sent at most once per day per organization.

Disabling auto-reload

Toggle it off under Dashboard → Billing → Auto-reload. Any in-flight reload completes; no further reloads are enqueued. Your saved card remains on file with Helcim (vaulted) and is not charged again until you re-enable.

What's next

  • Pricing & rate limits — per-model rates and rate-limit tiers
  • Errors — error shapes including payment_required and model_not_found

On this page