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

# Rate Limits

> Understanding JSONsilo rate limit

## Introduction

To ensure the stability and reliability of our platform, we have implemented rate limits across all API endpoints. These limits are designed to prevent abuse and ensure fair usage for all users. Below, you will find a detailed breakdown of the rate limits applied to each service.

If you require higher rate limits or have specific use cases that exceed these thresholds, please contact our support team to discuss potential solutions or upgrades to your plan.

## How Rate Limits Work

Each plan has two limits, and a request must pass both:

* **Burst limit**: How many requests you can send in quick succession. Think of it as a bucket that holds a fixed number of requests and drains at **1 request per second**. If the bucket is full, the request is rejected. A moment later there is room again.
* **Daily limit**: How many requests you can send in a 24-hour window. The window starts with your first request and resets 24 hours later.

If you exceed either limit, you will receive a `429 Too Many Requests` response with one of these messages:

| Message | Meaning | What to do |
| - | - | - |
| `Request limit exceeded` | You hit the burst limit. | Slow down and retry after a short pause. |
| `Daily limit exceeded` | You hit the daily limit. | Wait for the window to reset, or upgrade your plan. |

## Limits by Plan

| Plan | Burst limit | Daily limit |
| - | - | - |
| Free trial | 100 requests | 1,000 requests in total for the whole trial |
| Basic | 100 requests | 1,000,000 requests / day |
| Pro | 500 requests | 10,000,000 requests / day |
| Free (legacy) | 10 requests | 1,000 requests / day |
| Pro Plus & Lifetime (legacy) | 500 requests | 10,000,000 requests / day |

## What Each Limit Applies To

Limits are counted separately for each service, so heavy traffic on one doesn't use up another.

| Service | Counted per | Whose plan sets the limit |
| - | - | - |
| Private silo reads, including Query and Search | Silo | The silo's owner |
| Public silo reads | Silo | The silo's owner |
| Manage API | Account | The Manage Key's owner |
| MCP server | Account | The MCP Key's owner |

For example, on the Pro plan each of your public silos can serve 10,000,000 requests a day on its own.

## Rate Limit Headers

Successful responses include headers that show where you stand against the **daily** limit.

```
PrivateSilo-Req-Limit: 1000000
PrivateSilo-Req-Remaining: 999998
PrivateSilo-Req-Reset: 1755000000
```

| Header | Description |
| - | - |
| `*-Req-Limit` | Your daily limit. |
| `*-Req-Remaining` | Requests left in the current window. |
| `*-Req-Reset` | When the window resets, as a Unix timestamp in seconds. |

The prefix depends on the service:

| Service | Header prefix |
| - | - |
| Private silo reads | `PrivateSilo-Req-` |
| Public silo reads | `PublicSilo-Req-` |
| Manage API | `ManageSilo-Req-` |
| MCP server | `McpSilo-Req-` |

## Free Trial Limits

The free trial has one extra limit: **1,000 requests in total**, across your silo URLs, the Manage API, and MCP. Unlike the daily limit, this count never resets.

While you are on the trial, responses include these headers:

| Header | Description |
| - | - |
| `Trial-Requests-Limit` | The trial's total request limit. |
| `Trial-Requests-Remaining` | Requests left in your trial. |
| `Trial-Expires` | When the trial ends, as a Unix timestamp in seconds. |

### When the trial ends

Once the 2 days are up or the 1,000 requests are used, requests return `402 Payment Required` with this body:

```json theme={null}
{
  "error": "Trial ended",
  "code": "trial_ended",
  "reason": "time",
  "upgrade_url": "https://console.jsonsilo.com/billing"
}
```

`reason` is `time` when the 2 days have passed, or `cap` when the requests ran out. [Choose a plan](https://docs.jsonsilo.com/billing/upgrade-plan.md) to bring your silos back online.


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