Skip to main content
AI features in Cube use a token-based system to measure and manage consumption.

​
Overview

Cube’s AI-powered features consume tokens based on the resources required to complete each request. Token allocation differs by customer type:

​
Token consumption

Token usage depends on several factors:
  • Task complexity — More complex questions, multi-step analysis, or larger datasets consume more tokens than simple lookups. Each message in a session carries prior context, so longer sessions compound usage.
  • Data model context — Cube sends context from your data model to the LLM to improve answer accuracy. Larger models with more fields and descriptions use more tokens per request.
  • AI model — More capable models consume more tokens per request than lighter models.
Not all AI features consume tokens. The list of features that consume tokens is subject to change as the product evolves.

​
Per-seat token grants

On-demand customers on paid plans receive per-seat token grants equal to half of the seat price. Each user is awarded an individual monthly token allocation based on their role. Per-seat grants:
  • Are assigned to the individual user
  • Reset each billing cycle
  • Cannot be transferred, shared, or rolled over

​
On-demand consumption

When a user on an on-demand plan exceeds their monthly per-seat grant, usage automatically continues as on-demand consumption. On-demand usage is billed through the credit card on file. Administrators can set a monthly on-demand spending limit to control additional costs. This limit caps the total on-demand spend across the account for each billing cycle.

​
Token packages

Contract customers can purchase pooled add-on token packages. Token packages are added to a shared pool accessible by all users in the account.
  • Each package is valid for the duration of the contract or until fully consumed, whichever comes first
  • Multiple active packages can be combined
  • Packages do not auto-renew
Contact your account executive for details on purchasing token packages.

​
Free tier

Each user on a free plan receives an individual monthly token allowance. This allowance resets at the start of each calendar month.

​
Tracking usage

Remaining allocation from per-seat grants and token packages is shown on the Overview tab of the billing settings page. Detailed consumption is broken down on two further tabs:
  • AI Usage — token usage and spend (in dollars), per user or per role, over a billing period, with a chart and a table. Supports the account’s standard billing period presets as well as a custom date range.
  • AI Requests — the raw request log, defaulting to the last 24 hours, with a live tail of new requests as they come in.

​
When limits are reached

When a user exhausts all available token sources (per-seat grant and token packages), AI requests will return an error indicating the token limit has been exceeded.
  • Administrators are directed to the billing page to purchase additional token packages
  • Non-admin users are prompted to contact their account administrator to increase token quotas

​
FAQ

​
Do tokens roll over?

  • Per-seat grants reset each billing cycle and do not roll over
  • Token packages remain active for the duration of the contract

​
Can I bring my own AI model?

Yes. When using a Bring Your Own Model (BYOM) configuration, AI requests bypass the token quota system entirely — no tokens are consumed or tracked for those requests. You are billed directly by your model provider.

​
Why does a single prompt sometimes use more tokens than expected?

Cube’s AI features use an agentic architecture. A single prompt may trigger multiple internal steps — such as searching the data model, building a query, and summarizing results — each of which consumes tokens independently.

​
Why does the same question use different amounts of tokens?

Token usage can vary between identical prompts due to differences in conversation context (earlier messages in the session) or the AI choosing a different reasoning path.