Sari la conținut
KlusAI Docs

Credits and billing

Acest conținut nu este încă disponibil în limba selectată.

razorBridge is prepaid. An account holds a balance of credits denominated in euros — one credit is one euro — and every AI Blade and every inference call draws that balance down. There is one balance and one ledger per account: no separate bill for compute and inference, and no invoice to reconcile afterwards.

Where credits come from

Section titled “Where credits come from”
  • Signup credit. An account is created the first time you open razorBridge in the web app or approve an API sign-in, and it receives €10 immediately. The entry shows up in the ledger as Signup grant.
  • Grants. Additional credit is added by KlusAI on request. Email hello@razorbridge.eu with what you need it for; grants for courses and competitions are the normal route today.
  • Organization accounts. If you belong to an organization’s account, whoever manages its billing controls its balance; your blades draw on it.

Credits do not expire.

How GPU runtime is charged

Section titled “How GPU runtime is charged”

Each GPU type has a published rate in euros per GPU-hour. The rate is read from the live pricing catalogue, which is what the pricing page and GET /v1/gpu-types/ both show. It is per blade, so an event using ten blades bills ten times the rate.

The charge is calculated from the blade’s elapsed wall-clock time, in hours to two decimal places (36-second steps), multiplied by the rate. There is no rounding up to the minute or the hour and no minimum charge — a 7-minute blade costs about 7/60 of an hour.

A self-serve session holds credit before it starts: the cost of the whole duration you chose, at the rate shown when you started it. Extending the session enlarges the hold. Held credit is not spent, but it is not available either — a second session or an inference call that needs more than your balance minus your holds is refused. When the session stops, you are charged for the time it actually ran, never more than the hold, and the rest is released. A session that never reached Running releases its hold without a charge.

Timing matters when you read your balance:

  • While a blade runs, its accumulated cost is recomputed every few minutes and shown on the session row. It is not yet in the ledger.
  • The ledger entry is written once, when the blade stops. For an event, one entry covers all of that event’s blades.

So a balance that looks untouched mid-session is normal. Holds do not appear in the ledger; the in-flight cost is still counted against your monthly cap and against the balance check that stops a session when it would run out of money.

How inference is charged

Section titled “How inference is charged”

Calls to razorBridge AI Gateway are billed per token, based on the model used, and converted to euros. Before a call is sent, the most it could cost is held from your available credit; when it completes, the actual cost is deducted from the same balance with the source inference and the rest of the hold is released. Each call also writes a usage record. Charges appear as soon as the call completes — unlike GPU runtime, there is no wait until teardown.

See razorBridge AI Gateway for per-key restrictions and budget caps.

Reading your ledger

Section titled “Reading your ledger”

Open Credits in the web app, or call GET /v1/credits/ for the same balance and history in machine-readable form. Every entry has a type (credit or debit), an amount in euros, the balance after it, a description and a source that tells you what kind of movement it was:

Source What it means
grant Credit granted, including the €10 signup credit
manual An adjustment made by KlusAI
invoice Credit against an invoice
voucher Credit from a voucher
stripe Credit from a card payment (not in use yet)
consumption A debit for AI Blade runtime
inference A debit for AI Gateway usage
refund Credit returned to the account

Ledger entries are immutable: a correction is a new entry, never an edit. A historical entry always reflects the rate that was billed at the time, even if the published rate has changed since.

Running out

Section titled “Running out”

Low balance is enforced in three places, in increasing severity:

  1. A warning email goes out — at most once a day — when your effective balance is worth less than about an hour of your current burn rate.
  2. New work is refused. Starting a session that your available credit cannot cover fails up front with the amount needed, and an inference call whose maximum cost your available credit cannot cover returns HTTP 402 Insufficient credits.
  3. A running blade is stopped. If its accrued cost reaches your available balance, the blade is torn down at the next metering cycle rather than being allowed to run up a debt.

Account guardrails

Section titled “Account guardrails”

Beyond the balance itself, each account carries limits that cap accidental spend — by default 2 concurrent self-serve blades, an 8-hour maximum session, and €50 of spend per calendar month. Hitting the monthly cap produces an explicit error naming the cap and how much of it you have used. Ask KlusAI to raise them if your course or project needs more; see razorBridge AI Blades and sessions.

Section titled “Related pages”