Billing
Credits, subscriptions, and top-ups for community owners.
Billing is managed per billing owner (your personal account, or an organization you own or administer). You manage it in Settings → Billing.
What you see
- Credit balance — your available credits, broken down by grant source.
- Subscription — your current plan; you can subscribe or start a free trial.
- Top-ups — buy a pack of extra credits.
- Recent activity — recent credit consumption.
Checkout and plan management go through Stripe (a hosted checkout and the Stripe Customer Portal). If you own or administer an organization, a context switcher lets you view and manage organization billing separately from your personal billing.
What uses credits
AI-heavy operations consume credits — most notably search and enrichment. Enrichment shows a credit estimate and an over-budget warning before you launch a run (see Enrichment).
Metering is live; hard blocking is not (yet). Distinguish two things:
- Debiting (metering) — in production, credit debits are active for a set of operations (post-hoc markers actually deduct credits today).
- Blocking (enforcement) — no operation hard-blocks on an insufficient balance today;
enforcement_enabledis off for every op. The one hard limit that does block is the trial entitlement cap (community and profile limits). The in-event AI interview debits credits inline, but it does not refuse on a low balance yet.
Enforcement is being rolled out in stages, so what blocks (vs. only debits) may change.
Billing behavior is evolving. For the authoritative, current state of what's metered vs.
enforced, see
docs/BILLING_ARCHITECTURE.md
and the prod cutover checklist.