> For the complete documentation index, see [llms.txt](https://docs.tardis.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tardis.dev/api/rate-limits.md).

# API Rate Limits

Subscription plans include daily and monthly data transfer limits. These limits apply to the total compressed data transferred through [downloadable CSV files](/downloadable-csv-files/overview.md) and [raw data replay API](/api/quickstart.md) responses across API keys in the same account.

This page covers two different limits:

* **Data transfer limits** count compressed bytes served by CSV downloads and raw data replay API responses.
* **Raw data replay request limits** count underlying `/data-feeds` requests generated by historical replay.

## Data Transfer Limits

| Subscription type | Perpetuals / Options             | Spot / Derivatives                | All Exchanges                    |
| ----------------- | -------------------------------- | --------------------------------- | -------------------------------- |
| Academic          | <p>10 TB/month<br>0.5 TB/day</p> | <p>15 TB/month<br>0.75 TB/day</p> | <p>20 TB/month<br>1 TB/day</p>   |
| Solo              | <p>20 TB/month<br>1 TB/day</p>   | <p>30 TB/month<br>1.5 TB/day</p>  | <p>40 TB/month<br>2 TB/day</p>   |
| Professional      | <p>50 TB/month<br>5 TB/day</p>   | <p>75 TB/month<br>7.5 TB/day</p>  | <p>100 TB/month<br>10 TB/day</p> |
| Business          | <p>150 TB/month<br>25 TB/day</p> | <p>200 TB/month<br>35 TB/day</p>  | <p>300 TB/month<br>50 TB/day</p> |

Daily limits reset at 00:00 UTC. Monthly limits reset at 00:00 UTC on the first day of each calendar month. These limits count compressed data served, not uncompressed payload size.

## Raw Data Replay API Request Limits

[Raw data replay API](/api/quickstart.md) is available for Professional and Business subscriptions and has these additional daily request limits:

| Subscription type | Perpetuals / Options | Spot / Derivatives | All Exchanges   |
| ----------------- | -------------------- | ------------------ | --------------- |
| Professional      | 10 million/day       | 20 million/day     | 30 million/day  |
| Business          | 50 million/day       | 75 million/day     | 100 million/day |

Per-minute raw data replay request limits:

* Professional: 10,000 requests/minute
* Business: 40,000 requests/minute

Per-minute request limits are counted at the account level across API keys. A single API key can be used only from a single IP address at the same time.

Raw data replay request limits are consumed by the `/data-feeds` requests behind replay, not by the number of client `replay()` calls. One replay call can still issue many `/data-feeds` requests when it covers a long time range or many channel/symbol filters.

{% hint style="warning" %}
Compression affects data transfer only. It does not reduce raw data replay request count.
{% endhint %}

## Use the API Efficiently

{% hint style="info" %}
Use Tardis.dev as an on-demand historical data source: fetch only what the current job needs, keep local caches, and fetch more later.
{% endhint %}

### Reduce data transfer

* Official [Node.js](/node-client/replaying-historical-data.md) and [Python](/python-client/replaying-historical-data.md) clients request replay data with `zstd` compression by default and cache fetched slices locally.
* For direct HTTP API calls, set `compression=zstd` or `compression=gzip`; the `Accept-Encoding` header must allow the selected encoding.
* Filter raw replay by exchange, channel, symbol and time range instead of fetching broad ranges upfront.
* Use [downloadable CSV files](/downloadable-csv-files/overview.md) when normalized daily files fit your workflow. CSV datasets are gzip-compressed and split by exchange, data type, symbol and day.
* Download only the data types, symbols and dates needed for the current job.

### Reduce raw data replay request count

* If you need all symbols for a channel, request that channel once by omitting `symbols` or passing `symbols: []`. Do not loop through symbols one by one.
* If you need selected symbols, put them in one filter for the same exchange, channel and time range instead of one request per symbol.
* Keep local caching enabled so repeated runs can reuse fetched slices.
* For direct HTTP API calls with filters, use the [`x-suggested-slice-size`](/api/http-api-reference.md#data-feeds-exchange) response header as the next `sliceSize` for the same exchange, filters and compression.
* Keep replay job concurrency controlled. More than about 60 parallel `/data-feeds` requests does not improve throughput.

All-symbol filters require access to all symbols for the exchange. Limited-scope subscriptions must provide explicit symbols in filters.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tardis.dev/api/rate-limits.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.