AI Credits and Usage Allowances

AI credits and usage allowances set how much AI generation a plan includes, what each task consumes, and when extra use costs more.

AI credits and usage allowances measure how much of an AI service you can use under a plan. A credit may be a prepaid balance or an in-product unit consumed by a task; an allowance may instead cap messages, requests, or activity over a time window. Each service defines its own meter, so one vendor’s credits do not convert into another’s.

What to compare

For an author, the useful measure is what the plan can handle: a few chapter revisions, a long manuscript analysis, or repeated image generations. Check which models and features consume the allowance, how much a typical task uses, when the counter resets, whether unused credits expire or roll over, and whether top-ups, overages, or a hard stop apply. Also check whether the app subscription includes model-provider usage or bills it separately.

The units can work differently even within one service. Adobe says its monthly generative-credit allocation depends on the plan and that each feature may consume a different amount (Firefly credit overview, checked 3 October 2026). OpenAI’s prepaid API credits are a balance that decreases with API use, while token rate limits and monthly spend limits are separate (prepaid billing documentation, checked 3 October 2026). Compare each plan’s own meter rather than treating its credit count as a universal measure.

All glossary terms →