Usage & Limits
Understand how usage is tracked, quota limits per plan, and how to monitor your consumption.
How usage is tracked
CLAIV Memory tracks usage across several dimensions per billing cycle:
Requests
Total API calls across all endpoints (ingest, recall, forget).
Ingest events
Number of events ingested. Each POST to /v1/ingest counts as one event (even if deduped).
Tokens
Total tokens processed across recall responses. Measured via token_estimate in recall responses.
Work units
Internal compute units consumed by enrichment processing. Varies by event complexity.
Plan limits
| Metric | Free | Starter ($29/mo) | Growth ($99/mo) | Enterprise |
|---|---|---|---|---|
| Ingest events | 1,000 | 50,000 | 500,000 | Custom |
| Recall requests | 10,000 | 500,000 | 5,000,000 | Custom |
| Projects | 1 | 3 | 10 | Unlimited |
| Data retention | 7 days | 30 days | 1 year | Custom |
Quota enforcement
When you exceed a quota limit, the API returns a 429 status code with error code quota_exceeded.
{
"error": "quota_exceeded",
"message": "Monthly ingest limit exceeded",
"reset_date": "2026-03-01T00:00:00Z"
}Quotas reset on the first day of each billing cycle. You can check your current usage and remaining quota in the console under Usage & Limits, or via the usage API endpoints.
Monitoring usage
There are two ways to monitor your usage:
Console dashboard
Open any project from your Dashboard and click the Usage & Limits tab to see a visual breakdown of your usage with quota progress bars, endpoint breakdown, and range selection (today, 7d, 30d, this month).
Usage API
Programmatically check usage via the API:
GET /v1/usage/summary?range=30d— Totals for a time rangeGET /v1/usage/breakdown?range=30d— Per-endpoint metricsGET /v1/usage/limits— Current quota status
Backend API key
The console queries usage data from the CLAIV Memory backend using a Backend API Key that you configure in Settings. This key is stored encrypted on the server and never exposed to the browser.