Opsmeter.io
AI Cost & Inference Control
Integration docs
Implementation guide for AI cost control
Ship telemetry fast, keep attribution stable, and move from ingest to governance without changing your app network path.
Recommended path
Start with direct ingest, validate one stable payload shape, then harden budgets, retries, and incident workflows.
What this page answers
- What raw versus summary retention means in practice.
- How exports and dashboards behave when older raw data expires.
- What upgrades change and what they do not restore.
Implementation rhythm
5 minfirst ingest path
No proxyapp path unchanged
One schemaacross providers
Use quickstart for initial payloads, then operations docs to harden production workflows.
Retention & data lifecycle
Opsmeter.io keeps raw request rows and daily summary rows with different windows. Raw data powers detail tables (top users/endpoints/prompt versions). Summary data keeps long-term trend visibility.
| Plan | Raw retention | Summary retention |
|---|---|---|
| Free | 14 days | 90 days |
| Starter | 30 days | 180 days |
| Pro | 90 days | 365 days |
| Team | 180 days | 730 days |
| Enterprise | Unlimited (configurable) | Unlimited (configurable) |
What users see in analytics
- If your selected range starts before raw retention, detail tables are truncated.
- Overview/trends can still show aggregated history from daily summaries.
- UI shows inline “Retention window applied” messaging with available range start.
Upgrade behavior
Upgrading a plan does not restore already purged raw rows. Newly increased retention applies going forward. Historical summary trends remain available when retained.
Export behavior
CSV/JSON exports follow the same retention windows as Dashboard queries. Older ranges can be truncated. Export responses include retention metadata headers (X-Retention-Truncated, X-Retention-Available-From-Utc).
Related docs: Data modes, Integration samples, Pricing plans.