> ## Documentation Index
> Fetch the complete documentation index at: https://docs.primeintellect.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing and settings

> Understand trace charges, workspace limits, and automatic upload controls

## Pricing

Prime Traces is priced by data volume:

| Usage | Price |
| - | - |
| Ingestion | **\$1 per GiB ingested** |
| Storage | **\$0.10 per GiB per month stored**, billed hourly |
| Requests | **No request fees** |
| Egress | **No egress fees** |

One GiB is 1,073,741,824 bytes. Ingestion is charged when data is ingested; storage depends on the volume retained over time. For illustration, ingesting 10 GiB and retaining it for approximately one month costs approximately \$11: \$10 ingestion and \$1 storage.

Trace charges are separate from training, inference, and other platform usage. Exporting legacy samples is free, but data subsequently uploaded to Prime Traces incurs the rates above.

## Control run uploads

Prime Traces is enabled by default. Traces uploaded by platform runs incur ingestion and storage charges.

To disable uploads for a workspace:

1. Select the appropriate personal or team workspace.
2. Open [Billing → Usage Limits](https://app.primeintellect.ai/dashboard/billing?tab=limits).
3. Disable **Upload runs to Prime Traces**.

Turning off uploads does **not** delete stored traces. Existing traces remain viewable in the dashboard; account-level opt-out also disables trace reads through the SDK and CLI. See [Viewing and deleting traces](/traces/managing-traces) to manage existing data.

## Opt out for a run or client

The controls below are documented in the [Prime Runs SDK at CLI release v0.9.4](https://github.com/PrimeIntellect-ai/prime/blob/v0.9.4/packages/prime-runs/README.md#opting-out-of-prime-traces). Update older installations before using them; separately installed SDKs must also include these controls.

For a single run, pass `traces_opt_out=True` to your existing `prime_runs.init(...)` call. For a shell or job:

```bash theme={null}
export PRIME_TRACES_OPT_OUT=true
```

For runs using this machine's Prime configuration:

```bash theme={null}
prime config set-traces-opt-out true
```

Client setting precedence is: explicit `init()` argument, then `PRIME_TRACES_OPT_OUT`, then the config file. These client controls do not override an account-level opt-out. They control Prime Runs routing; they are not a substitute for workspace permissions on standalone Traces API requests.

Opted-out runs use legacy sample storage while that service remains available. This is a temporary compatibility path, not permanent free trace storage. See the [November 6 retirement and export instructions](/traces/legacy-storage).

To allow uploads again, enable them for the workspace and remove or set to `false` any applicable client opt-out. Change the setting before starting the run.

## Usage limits

Check the selected workspace's [Usage Limits](https://app.primeintellect.ai/dashboard/billing?tab=limits) when an upload fails because storage is over its limit. Verify the workspace first, then review its configured limit and stored data. See [deletion and quota troubleshooting](/traces/managing-traces#troubleshooting).

A usage limit and a pricing rate are different: the limit controls available capacity; the rates above determine charges for accepted usage.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.