For the complete documentation index, see llms.txt. This page is also available as Markdown.

Export

Create and deliver Control Center data exports on your schedule.

Create files from Control Center datasets and deliver download links by email or webhook. Exports run once or follow a recurring schedule.

Exports run in the background. You don't need to remain on this page.

Plan an export

Start an export from Control Center → Observability → Export. Scope the export to every project or one project. The project scope starts as All projects, even when you previously narrowed the export history.

Decision
Available choices
Default
Result

Project scope

Every project or one project

All projects

Limits the included data

Delivery

Email or webhook

Email

Sends a download link

Run type

Scheduled or one-time

Scheduled

Creates a recurring definition or immediate run

File format

CSV, JSON, or PDF

CSV

Defines each generated file

Give the export a clear name, such as Weekly audit trail export. You must provide a name and select at least one dataset. Webhook delivery also requires an HTTPS URL.

Choose data

Select the datasets that you need. Each dataset generates its own file. Selecting two datasets produces two files, not one merged workbook.

Dataset
Contents
Best for

Credit Usage

Consumption by app, agent, and model over the selected period

Cost analysis

Platform Analytics

Platform, app, and agent events with the initiating user

Platform activity analysis

App Analytics

Published-app sessions, visitors, page views, and duration

App usage analysis

Agent Analytics

One row per traced operation, including trace, parent, summary, and duration

Agent performance analysis

Audit Trails

Configuration and access changes with the responsible user and time

Compliance review

AI Gateway Logs

Provider, token usage, cost, and latency for every model call

Model operations analysis

Eval Results

Scores, verdicts, reasoning, and human overrides for evaluated agent runs

Agent-quality analysis

At least one dataset is required. A multi-dataset export creates a separate file for each dataset.

Set delivery

Send the download link to one or more recipients.

Setting
Value
Behavior

Recipients

Comma-separated email addresses

Sends the link to each address

Empty recipients

No address

Sends the link to your signed-in account

Send the download link to an HTTPS endpoint that you control.

Setting
Required
Behavior

Webhook URL

Yes

Receives a POST request with the download link

Signing secret

No

Signs the request for endpoint verification; you can reveal the masked value while entering it

Schedule delivery

Choose a recurring schedule when you need regular files. Choose a one-time run when you need one historical range.

Run type
Timing
Stored definition
Data period

Scheduled

Hourly, daily, weekly, or monthly

Yes

The period for that run

One-time

Starts immediately

No

Your selected time range

For scheduled exports, the default frequency is daily and the default UTC time is 02:00. Daily runs cover the previous 24 hours. Weekly runs start on Monday. Monthly runs start on the first day of the month. You can't change either weekly or monthly anchor.

For a one-time export, select Today, Yesterday, Last 7 days, Last 30 days, This Week, This Month, or Last Month.

Confirm and run

Review the summary before saving or running the export. It shows the frequency or date range, project scope, dataset total, format, and delivery method.

A scheduled export creates a reusable definition. A one-time export creates only a completed run.

Use these examples to validate the intended configuration:

  • Weekly at 08:00 UTC · All projects · 1 dataset · Csv → Email

  • Runs once, starting now · Jul 1, 2026 – Jul 31, 2026 · <project> · 2 datasets · Json → Webhook

Track and update exports

Saved export definitions retain their project scope, datasets, cadence, delivery, and format. Update a saved definition to change future runs.

Completed runs include one-time and scheduled exports. Each run records the requested time, project, datasets, delivery method, format, row total, and status. Status vocabulary can vary by environment.

If an email or webhook doesn't arrive, retrieve the file from the completed-run history while its download link remains valid. Refresh the history to retrieve the latest run state.

Last updated