Credits & budgets

Open Vertex Router bills usage from a prepaid balance you top up in USD. Usage across every provider draws down from it, and you receive one invoice instead of one per vendor. An optional credit line lets traffic continue past a zero balance, up to a monthly limit. Either way, spending stops at a hard line instead of running on.

How a request is billed

Each request is priced from its token usage and debited from your account after it completes. The cost shows up per request in Logs and aggregated in Statistics; it is not returned in API responses. All keys of the account draw from the same balance. Requests refused by the gateway, for example for a rate limit or an unknown model, are not billed.

Your plan subscription (Starter, Team, Scale or Enterprise) is invoiced separately from usage.

Prepaid balance

• Top up from the Billing page of the dashboard, by card. A top-up is between $100 and $10,000. Bank transfers can be arranged with our team.
• The balance is credited as soon as the payment is confirmed, and it carries over from month to month.
• Prepaid funds are always consumed first.

Credit line

The credit line is off by default. Our team enables it for an account on request, with a monthly limit in USD.

• It is used only once the prepaid balance reaches zero.
• Credit usage is counted per calendar month (UTC) against the limit.
• It is invoiced at the start of the following month as “Usage for” that month, on the payment terms agreed for your account. An account that only uses prepaid funds never receives a usage invoice.

When the money runs out

When the prepaid balance reaches zero with no credit line, or the credit line’s monthly limit is reached:

• The request that crossed the line is still served and billed.
• Every later request, with any key of the account, is refused with 401 and a message saying the key is blocked. Creating new keys is refused as well.
• There is no overage. Nothing is served beyond the limit.
• Top up from the Billing page. This is allowed while the account is blocked, and the block lifts as soon as the payment is confirmed.

An invoice left unpaid for more than 14 days suspends the account in the same way until it is paid.

Caps you can set yourself

• Per-key budget. When creating or editing a key on the API keys page, set a budget in USD. The budget covers a rolling 30-day window from the moment it is set, not a calendar month. Once it is used up, that key gets 429 until the window resets; the other keys are not affected. See Rate limits to tell the two 429 cases apart.
• Allowed models per key. A key restricted to the models you have validated cannot be used on more expensive ones. See Models & providers.
• Alerts. On the Alerts page, opt in to an email when the prepaid balance falls below a USD threshold, and to emails when credit usage reaches given percentages of the monthly limit. The billing contact always receives them; you can add other recipients.

Budgets exist per key and per account. There is no budget per workspace or per tag; use request tags to see where spend goes, and key budgets to cap it.