Export, usage, and limits
Understand data export, usage visibility, retained resources, and blocked-at-limit behavior.
Export your workspace data, read your current usage, and know exactly what happens when a plan limit is hit.
Export run data
Use GET /api/export to retrieve a bounded JSON or CSV export for the current workspace and project context. Filtered exports use the same run filters and search language as GET /runs; selected-run exports pass run_ids (or runs) with up to 100 run UUIDs. Add format=csv for a flat spreadsheet-safe record stream. In the dashboard, the Runs command bar uses this route for selected-run CSV downloads.
Typical export contents include:
- Projects.
- Runs.
- Scalar metric history.
- Attributes and rich object metadata.
- Artifact metadata.
- Import records.
- Limit/truncation metadata.
Use export for backups, migrations, debugging, and vendor evaluation. Synchronous exports are capped:
| Export cap | Limit |
|---|---|
| Filtered runs | 500 |
| Selected run IDs | 100 |
| Metric points | 100,000 |
| Metric-series summaries | 25,000 |
| Attributes | 25,000 |
| Artifacts | 10,000 |
| Table rows | 25,000 |
| Import records | 500 |
| CSV response size | 25 MiB |
Export charts
Metrics and Runs workspace line charts include opt-in export buttons for the visible graph. Chart CSV export is the plotted sample, not a full raw-history archive; SVG image export renders the visible graph in the browser. These controls are capped at 120 series and 20,000 plotted points. Use selected-run CSV export or filtered API export when you need raw run data.
Check usage
Use GET /api/usage to inspect plan catalog data, current workspace usage, limits, and overage policy.
Usage includes:
- Seats.
- Projects.
- Runs.
- Current-period metric points.
- Current-period API requests.
- Retained metric points.
- Metric series.
- Artifacts.
- API keys.
- Artifact bytes and metadata estimates.
Know which counters reset
Some counters reset every month; others count everything your workspace retains.
| Counter | Reset behavior |
|---|---|
| Metric points | Current UTC calendar month |
| API requests | Current UTC calendar month |
| Projects | Retained resource |
| Runs | Retained resource |
| Seats | Retained resource |
| Storage | Retained resource |
| Artifacts | Visibility-only retained count |
| API keys | Retained resource |
Handle blocked-at-limit errors
When a blocked limit would be exceeded, write routes return a plan-limit error instead of accepting a partial write.
Affected write paths can include:
- New projects.
- New runs.
- Metric ingest.
- Artifact storage writes.
- Imports.
- Demo reset.
Short-window API request limits return 429 with Retry-After, RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers. Monthly API request quotas reset at usage_period.reset_at: Free and non-billable workspaces are blocked at the allowance, while paid Pro/Premium overage is Stripe-metered.
Export usage data
Use GET /api/usage/export when you need versioned usage data for operations or support workflows.