Plans and Limits

AIVAX has three account plans: Free, Pro, and Max. The current plan controls model access, account-level rate limits, storage quota, conversation retention, and included daily service allowances.

For commercial subscription prices and plan packaging, use the AIVAX pricing page. This page documents account-level limits only. Limits that belong to a specific product, such as RAG searches, web search, Agentic Tests, or Batch, are documented in that product’s page.

Account limits #

An em dash (—) means the plan does not impose a limit. Model, gateway, provider, or product-specific limits may still apply.

Integrated model requests are limited by both request count and input tokens. Model rate-limit groups adjust the request-count thresholds:

For example, a Pro account normally has 200 integrated-model requests per minute. With a Discounted model group, the adjusted threshold is 100 requests per minute.

BYOK uses a provider key configured on the gateway instead of an integrated AIVAX model, but requests still pass through AIVAX infrastructure and use the plan’s BYOK limit.

Rate limits are shared across all API keys of the same account. A request that would exceed an active window returns 429 Too Many Requests; pace requests and use bounded retries with backoff.

Custom accounts use the Pro plan limits multiplied by a factor agreed for the account, or have no plan rate limits when no factor is set.

Included daily subscription allowances #

Free, Pro, and Max include separate daily allowances for the services below. Each comparison refers to the same service on the named plan, not to a shared credit balance or a guaranteed number of requests. Unused allowance from one service cannot cover another. Custom accounts do not receive subscription allowances.

RAG searches and document insertions share the embedding allowance. It does not cover answer generation, media processing, text classification, or segmentation. A query embedding served from cache does not consume it. Reflex uses a separate reranking allowance that includes both cached and uncached input. The semantic decision allowance covers only eligible decision models; see Semantic Decisions. Optional Fetch JSON conversion is separate from the extraction allowance.

Coverage is evaluated for each metered service item: a document’s embedding, an individual query-term embedding, a reranking call, a decision call’s input usage, or an extraction operation. Each item is either fully included or billed in full at normal rates. Included items are tracked in subscription consumption, not as zero-cost entries in billing history. The current allowances permit a 10% margin above their base capacity. An item that would exceed that margin leaves the allowance unchanged and is billed normally. One request can contain several items, so some may be included while others are charged.

Daily allowances reset at midnight in the server’s local time. Check the account’s subscription usage indicators for consumption and reset status; usage can exceed 100% while within the margin. LLM subscription coverage is currently disabled, so text-model inference and RAG answer generation remain metered separately. Allowances do not bypass balance requirements or rate limits. See Pricing for how uncovered items are billed. For a walkthrough of testing a retrieval pipeline within these allowances, see Free RAG API: embeddings, reranking and OCR limits.

Public API keys #

Public keys have additional limits independent of the account plan.

Public keys can be used for RAG semantic search, RAG answer generation, speech generation, media descriptions, image generation, and chat completions. For chat completions, public keys also require a full AI Gateway UUID, restrict request parameters, and omit server-side tool surfaces. See Authentication.