Credits & Billing

OpenModels uses credit-based billing. Add credits to your account, then spend them across supported models through your API keys.

Credits

Credits are the account balance used to pay for model usage.

• Credits are shared across supported models.
• Credits are shared across API keys in the same account.
• Requests consume credits according to the selected route’s pricing unit.
• If the available balance is too low, requests can fail with key_market_insufficient_balance.

Add credits

OpenModels supports multiple funding methods:

Crypto payments are confirmed through the payment provider before credits are added to your balance.

Plans

Current active plan data:

Monthly plans add credits to your OpenModels balance each billing cycle.

How credits are consumed

For token-priced models, usage is calculated from input and output tokens:

credit spend = input token cost + output token cost

The exact price depends on the selected model. See the Pricing Guide and Models page before routing production traffic.

Balance checks

OpenModels checks account balance before processing requests. If the account has no available balance, the gateway can reject the request before sending it upstream.

If a request fails because of balance:

1. Add credits or enable auto top-up.
2. Confirm the balance is active in the dashboard.
3. Retry the request.

API key limits are separate

Credits are account-wide. Monthly spend limits are configured per API key.

Use monthly spend limits to prevent a single key, application, or environment from consuming more than intended.

Billing visibility

Use the dashboard to monitor:

• Current credit balance
• Top-up history
• API key spend
• Model-level usage
• Request volume and token usage
• Monthly limit status

For production workloads, check credits and monthly spend limits before launch.