Plan credits are the user’s included AI allowance from their subscription. Example flow: User subscribes to a plan. The system activates the subscription. The system grants that plan’s included credit...
Upload a cover image in Admin Settings > System Manuals to replace this training placeholder.
Example flow:
User subscribes to a plan.
The system activates the subscription.
The system grants that plan’s included credits to the user’s AI credit balance.
When the user generates courses, images, speech, recognition, video-related assets, or other metered AI work using the platform keys, usage is recorded and charged against those credits.
Each AI call estimates/measures cost and deducts credits from the user’s balance.
When the credits run out, on-demand billing takes over if enabled.
So the handoff is:
Subscription plan -> included AI credits -> AI usage consumes credits -> credits depleted -> on-demand invoice billing
Credits are used against platform-funded AI usage, not BYOK usage. If a user brings their own API key, the system can still log/audit usage, but it should not debit platform credits because the platform is not paying the provider bill.
When credits are depleted:
If on-demand is enabled and the user is eligible, AI continues working.
The system starts accumulating on-demand charges.
It creates invoices at thresholds like $50, $100, then continuing $100+ (Institutional Layer) bands.
The user can pay those invoices through PayPal/PayFast/etc.
Admin can manually settle, write off, top up, or make the user unlimited.
If on-demand is disabled or the user is blocked by admin usage controls, then AI usage should stop once credits are depleted. On-demand lock enforcement so outstanding on-demand invoices pause all AI routes until paid.