Usage
How usage is calculated
Usage is calculated by counting billable operations — writes and recalls. Everything the meters show traces back to those operations.
Billable operations
Each billable op is one of three kinds, and the dashboard breaks your total down the same way:
- Writes — facts saved to memory.
- Recalls — memory lookups.
- Gated recalls — recalls run through the metamemory gate (answer / verify / abstain).
Billing-period quota and reset
Your plan's quota covers one billing period. The counter tracks the current period and resets when it ends: on a paid plan the period follows your billing cycle; on the free plan it's the calendar month (UTC). The usage card in your dashboard shows the period and the exact reset time in your local time.
Session windows
Alongside the period quota, usage is tracked in session windows — 5 hours, daily, and weekly— each with its own cap for your tier. A window starts with your first operation: your 5-hour session starts with your first operation and ends exactly five hours later, when its counter fully resets. Idle time never ticks — if nothing is running, no window is open. The dashboard's windows meter shows used-vs-cap per window and the exact reset time, in your local time.
From 80% of any enforced limit you get live warnings — in the dashboard and inside your AI chat, on every reply. At 100%, new writes pause until the window's exact reset time; recall keeps working the whole time, and upgrading adds capacity instantly. On the Free and Pro plans we also email you when your weekly window passes 80%.
On multi-seat plans (Teams, Business, Enterprise) the enforced limits are the 5-hour session window — per member and for the workspace collectively — plus the plan's monthly cap. Daily and weekly windows on those plans are analytics-only: tracked and displayed as usage feedback for admins and members, never blocking anyone.
Team usage
On multi-seat plans, members' billable ops count toward the team's plan quota. Owners see Team collective usage— the team's total billable ops against the plan's quota for the period, with the same writes/recalls breakdown — plus a per-member usagetable showing each member's billable ops.
Each member also has their own 5-hour session limit. Defaults are preset out of the box — the workspace's 5-hour pool split evenly across members — and owners and admins can raise or lower any member individually with the slider on that member's row on the Team page. Members see their own limits on their usage page.
Check usage from the API
GET /api/v1/usageCurrent-month billable ops + quota