The short answer
Alibaba's Token Plan Individual measures supported model and Harness-tool use in Credits. Every successful call consumes a variable number of Credits. The current official plan table publishes one seven-day limit for each tier: Lite, Standard and Pro.
When that documented limit is reached, plan calls pause rather than silently moving to pay-as-you-go billing. Alibaba currently describes three ways capacity can become available again: wait for the displayed reset, apply an available Reset Usage Limit benefit or purchase an eligible Credit Pack. Check the subscription console for the authoritative remaining balance and reset information. Coding Plan is a separate product with different quota units and rules.
What a Credit represents
A Credit is the plan's common usage unit; it is not the same thing as one prompt, one API request, one token or one US dollar. Alibaba says consumption is dynamically determined by the model, token usage, thinking mode and tool calls. A short request to an efficient text model can therefore consume differently from a long reasoning session, a web-search-assisted answer or a media-generation task.
The actual deduction and remaining seven-day allowance are shown in the subscription usage details, which is the appropriate place to evaluate a real workload. A generic conversion such as 'one Credit equals one message' would be misleading.
How the current seven-day limit works
The current official overview no longer publishes the previous short-window figures. Capacity comparisons should therefore use the seven-day limits that Alibaba documents now, not older short-window numbers retained in screenshots, articles or calculations.
- Lite currently includes 2,500 Credits per seven-day period.
- Standard currently includes 10,000 Credits per seven-day period.
- Pro currently includes 40,000 Credits per seven-day period.
- The subscription console is authoritative for remaining Credits, reset timing and any available reset or Credit Pack options.
A Standard-plan example
Standard currently has a 10,000-Credit seven-day limit. If representative interactive work consumes an observed average of 500 Credits per complete job, 10,000 divided by 500 gives a theoretical ceiling of 20 such jobs before allowing for other model calls, Harness-tool use, retries or changes in consumption.
That is an estimate, not a promised task count. The console's actual Credit deductions and remaining balance take precedence, and a user who reaches the limit should follow the reset, Reset Usage Limit or eligible Credit Pack options shown for the subscription.
This example explains timing, not how many coding tasks a plan guarantees. Credit deductions vary by request, and agent tools can make several model or tool calls while completing one user-visible task.
Current limits by tier
Alibaba also publishes recommended concurrent-agent ranges of one to two for Lite, three to four for Standard and six to eight for Pro. These are plan guidance, not a promise that every combination of model, task and network conditions will deliver identical throughput. Peak periods may involve queuing.
- Lite: 2,500 Credits per seven-day period; one to two recommended concurrent agents.
- Standard: 10,000 Credits per seven-day period; three to four recommended concurrent agents.
- Pro: 40,000 Credits per seven-day period; six to eight recommended concurrent agents.
What happens at the limit
When the documented quota is exhausted, Token Plan Individual blocks further plan calls rather than moving them automatically to pay-as-you-go billing. Current documentation directs users to wait for the reset, apply an available Reset Usage Limit benefit, purchase an eligible Credit Pack or consider a higher tier.
Plan features and promotional terms can change. Confirm the current plan page and checkout before purchase, then start with measured interactive use rather than assuming a monthly message count.