Credit metering in v1.2 was the plumbing. v2.1 is the surface — real billing cycles, pooled credits, and dashboards admins can actually read.
What shipped
- Monthly billing cycles — credits reset on a configurable anniversary day per organization. No more "we're out of credits" surprises mid-week.
- Organization credit pool — credits are shared across the org by default, not per-seat. Heavy users and light users average out.
- Admin credit overrides — admins can grant additional credits to specific users (e.g., the analyst running a big quarterly study), with an org-pool cap so this can't be abused.
- Pending credits widget — credits committed to in-flight conversations show separately from settled spend.
- Usage dashboard —
Settings → Usageshows current cycle, projected burn rate, per-agent breakdown, and per-user roll-ups. Drill into any user to see their last 100 prompts. - CDC artifact sync — change-data-capture between the Django side and the agent side means artifact metadata is always current without polling.
Why it mattered
Until v2.1, every paying customer needed manual usage tracking on our side. v2.1 ended that. Admins can now see what their team is doing, what it's costing, and which projects are driving the most usage — all from inside the product, in real time.
For admins
Usage dashboards live at Settings → Usage. Credit overrides live at Settings → Users → click a user → Credit override.