English
Português
Pricing
AIVAX uses a prepaid account balance. Paid invoices add credit to the account, and usage records subtract from that balance.
The backend calculates balance as:
balance = paid, unexpired invoice total - usage total
Use the AIVAX pricing page for current commercial plan prices. This page documents billing behavior that is visible in the API source.
Credits and invoices
Credits are represented as invoices.
- Paid invoices increase the usable account balance until their expiration date.
- Unpaid payment invoices are created with a one-year expiration.
- Unpaid invoices older than three days are removed by cleanup.
- Expired paid invoices no longer count toward balance.
- Payment invoice creation requires at least 3 USD and is rate-limited.
Usage billing
Every billable operation writes one or more usage records. Each usage record has:
- Description.
- Unit price.
- Quantity.
- Optional model name.
- Usage category.
- Resources such as API key, gateway, or collection.
The final unit price is multiplied by the account tax multiplier and the current plan commission multiplier.
Per-request consumed credits
When a request reports usage, AIVAX includes the total credits charged for that request in the response header:
Consumed-Credits: 0.005
The value is a decimal number of credits, formatted with a period as the decimal separator. It is the total for the complete request, including all billable operations performed while processing it. A tracked operation that has no charge can return Consumed-Credits: 0.
If the header is absent, the request did not report a usage total. Do not treat an absent header as 0. This header reports only the current request's consumption; use the account balance APIs to obtain the account's available balance or broader billing history.
| Plan | Commission multiplier |
|---|---|
| Free | 1.25x |
| Pro | 1.05x |
| Max | 1.00x |
Pricing list
- (1) Advanced internet search pricing applies to an external model connected to internet and search tools; the price varies based on the number of interactions performed by the agent.
- (2) Pricing for text extraction from media applies to a small omni-modal model, subject to availability.
- (3) Pricing for RAG response generation does not include the cost of query embedding; the price varies based on the summarization model.
- (4) Media Injector is billed for the aggregate input, cached input, output, and media usage produced while creating RAG documents. The source file, optional context, and generated content can all affect token usage. Standard account tax and plan commission multipliers still apply.
Inference billing
Integrated model billing uses the model's pricing table from the backend. Pricing can vary by model and by input-token threshold. Usage can include:
- Text input tokens.
- Cached input tokens, when the selected model has cached-input pricing.
- Audio input tokens, when applicable.
- Image input tokens, when applicable.
- Output tokens, including audio output tokens when applicable.
BYOK (Bring-Your-Own-Key) calls use your external provider key, but AIVAX still enforces BYOK request limits because the request passes through AIVAX infrastructure.
Balance requirements
Billable routes check balance before running. The generic balance middleware rejects balances below the route minimum; chat clients, integrations, and batch processing also stop when the balance is zero or negative. Some multimodal chat-completion inputs require a minimum balance before the model call starts:
| Input type | Minimum balance |
|---|---|
| Image or audio | $0.10 |
| File or video | $0.50 |
If the account balance is too low, the API returns 402 Payment Required.
Plans and limits
Plans affect both price and operation:
- Model access.
- Commission multiplier.
- Request and token rate limits.
- BYOK request limits.
- RAG quotas.
- Tool limits.
- Storage quota and overage price.
- Conversation retention.
- Subscription-model reserve windows.
See Plans and limits for the technical quota matrix.