End-user credits and plans
End-user credits are technical usage units for answers in a specific chatbot. They are not a balance, not a wallet, not e-money, and not payable out. A credit purchase allows more bot usage; it does not transfer money to other users.
Zeptix uses this language deliberately so that visitors understand: they are buying AI usage for a bot, not a financial product. At the same time, owners can still see which usage runs via the owner cap, the free reserve, or purchased end-user credits.
TL;DR — three pools
| Pool | Who uses it? | Purpose |
|---|---|---|
| Owner cap | Operator and free visitor usage | The plan's monthly budget |
| Free reserve | Public free usage | Controlled free answers |
| End-user credits | Paying visitors | Additional usage in the bot |
Credit purchase vs. end-user plan
A credit purchase is flexible: visitors buy a quantity of credits and consume them through answers. An end-user plan is recurring: visitors regularly receive a usage allowance for the bot. Both models stay tied to the bot and do not count as a freely transferable balance.
For many communities, a credit purchase is the simpler start. Recurring end-user plans fit when the bot delivers premium knowledge on an ongoing basis, for example coaching, learning support, or community support.
Why purchased end-user usage does not draw on your owner cap
In the Zeptix-first model, the purchase covers the technical usage. That is why purchased end-user usage is handled separately from the normal owner cap. This prevents paying visitors from draining your monthly budget even though they just purchased additional usage.
Free usage, promotions, giveaways, and training remain separate topics. They still need to be limited so that a public bot does not answer without limit at the owner's expense.
What visitors should see
Good credit communication is concrete:
- "Credits are used for AI answers in this bot."
- "Credits are not payable out and not transferable between users."
- "When credits run out, you can buy new credits or wait, in case a plan provides new usage."
Avoid terms like "withdraw balance", "wallet", or "account money". These terms create false expectations and do not match the technical usage unit.