Usage, quotas & limits
The Usage page (kariant.app/klick/usage) shows your real AI consumption across every Klick feature — the same counters the platform enforces.
How enforcement workslink
- check_circleEvery AI action is metered against a per-feature pool (chat, search, grounding, images, voice minutes and more) across daily/weekly/monthly windows.
- check_circleWhen a free-tier pool runs out you get a clear block message with the option to continue on Koins — nothing fails silently.
- check_circleConsumption is recorded per role and domain, so your user and partner activity are attributed separately while drawing on the same wallet.
When a feature is blocked or switched offlink
- check_circleMetered AI actions need an account. Open an account-only Klick surface while signed out and you are sent to Klick’s own sign-in page instead of into a run that cannot be attributed to anyone.
- check_circleThe quota that decides your run is applied on Kariant’s servers at the moment the action executes. The counters in the app are a convenience read of the same data a moment earlier, so a page left open for a while can show more headroom than you actually have.
- check_circleKariant can switch an individual AI feature off by setting its per-user allowance to zero. While that is set, the feature is blocked up front for everyone with a clear message, rather than starting a run and failing partway.
- check_circleIf Klick cannot establish your remaining allowance at all, it refuses the action instead of quietly letting it through. Reload the page, confirm you are signed in, and try again.
Frequently asked questions
The Usage page shows headroom but the feature is blocked — why?expand_more
Quota is enforced server-side when the action runs, and the page is a slightly older read of the same counters. A block can also mean Kariant has switched that specific feature off — its allowance is set to zero regardless of what is left in your pool.
Do I need to be signed in to use Klick AI?expand_more
For anything metered, yes. A few surfaces give signed-out visitors a small free allowance, but account-only surfaces route guests to sign-in — usage has to be attributable to a wallet before it can run.