Questions, answered plainly.

US dollars. You top up in dollars, your balance is kept in dollars, and the rate card and every charge are in dollars too — a dollar you pay is a dollar in your balance, with nothing to convert.

Rates are in US dollars per million tokens, input and output priced separately. A single call often costs a fraction of a cent, so a charge is shown to six decimal places ($0.000123) rather than rounded away to $0.00. Your balance is shown to the cent and rounded down, so it never shows more than you have.

$1, and whole dollars after that. There is no minimum term and no subscription.

A call starts only when at least $1.00 is available — your balance, less anything held by calls already in flight — so no call begins on a balance too thin to pay for its answer. It is not a fee and nothing is taken for it: the call that starts can spend it. Below $1.00 available, calls are refused until you top up.

No. It stays on the account for as long as the account is open.

At the published selling rate for the model shown on Models, on the usage reported for that call. Before the call runs, its worst case is held against your balance, and the hold is released the moment the real figure arrives. A call that comes back with no usage is charged on an estimate instead — the prompt plus the text actually returned — and your usage page marks it as estimated.

No. A charge is clamped at zero, and the clamp is recorded so it can be seen on the account rather than silently absorbed.

A call that is refused, or fails before any of its answer reaches you, costs nothing. A streamed answer that breaks part-way is charged, when it stops, for what arrived — and the error you saw says so.

We store a hash of it, not the key. That means a stolen copy of our database cannot be used to spend your balance — and it also means we genuinely cannot show you the key again. Copy it when it appears.

It bounds what a leaked key can do. A key issued for one model can only call that model; it is refused on anything else, and nothing is charged for the refusal. Every new key names its model, and you hold one active key per model at a time: to issue another for the same model, revoke the one you have — or, in the last seven days before it expires, simply issue the replacement and let the old one lapse. A key issued before this rule, with no model, no longer calls anything: issue a key for the model you use.

Yes. The console lists the models you hold a live key for, and each of its calls is made with your key for that model — exactly as a call from your own code is. To chat with a model there, create a key for it on the API keys page. A key that is revoked or has expired takes its model out of the console; for thirty days the model is still shown there, with a link to create a new key.

The key's. Each key is for one model, and everything called with it — from the console or from your code — is recorded against that key and charged to your balance. The Usage page shows the key of each call, and whether it came from the console (portal) or the API.

Ninety days is the default because rotating a credential is a habit worth having. Thirty, ninety, three hundred and sixty five, or a custom number of days are offered, and so is no expiry — for integrations that genuinely cannot rotate. An expiring key stops working the moment its term is up; nothing is charged to it after that, and an expired key cannot be revived — issue a new one.

Revoke it and issue another. Revoking takes effect immediately.

Business details appear on billing documents only after they have been verified. You can use your balance straight away — verification changes what the invoice says, not what the account can do.

On the Settings page. Changing a business name, address or tax ID sends those details back for verification, because what prints on an invoice has to be checked.