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

# Rate limits and tiers

> Tiers, requests per minute and per hour, how a tier is reached, and size and time limits.

The account tier sets the requests per minute and per hour for each model. A limit is a ceiling, not a guarantee that every request within it succeeds — see [Terms of Service, section 2](/legal/terms-of-service#2-access-and-accounts).

## Tiers

Every account starts on the **Core** tier.

| Tier | Reached at (spend in one month) | Requests per minute | Requests per hour |
| - | - | -: | -: |
| Core | — | 10 | 300 |
| Pro | \$500 | 100 | 5,000 |
| Scale | \$10,000 | 300 | 15,000 |

The figures apply to each model separately. The **Tier and limits** page on the [platform](https://platform.fortytwo.network) shows the figures for the account. An account with individual limits shows the **Custom** tier.

Requests through OpenRouter or another router follow that router's limits.

### Moving up

* **What counts:** usage charged to purchased credits in one calendar month (UTC). The amount of credits bought does not count, and neither do promotional credits.
* **When:** any month that reaches the figure counts, including the current one.
* **How:** press **Request upgrade** on **Tier and limits** or on the **Account** page — see [Get help](/docs/support#higher-limits-or-a-tier-upgrade). Each request is reviewed. A new tier starts at the beginning of the next month at the earliest.
* **Keeping it:** a tier stays with the account. There is no downgrade.
* **More than Scale:** in the same form, choose **Enterprise API terms**. For on-premises or private cloud, see [Harbor](/docs/support#fortytwo-harbor-on-premises-or-private-cloud-for-your-organisation).

## How requests are counted

* The windows are rolling: the last 60 seconds and the last 60 minutes, not clock minutes.
* All keys of the account share the limits. Each model has its own count.
* Every admitted request counts, also one that fails later. A request refused at admission does not count.
* Over a limit, a request is refused with `429 rate_limit_exceeded` and a `Retry-After` header — see [Errors](/docs/errors#retries).

## Requests running at the same time

A separate limit caps how many requests from one account can run at once for each model, across all keys. It is not published and can change with the load. A request over it fails at once with `429 concurrency_limit_exceeded`.

The Terms allow Fortytwo to throttle or queue requests for a short time to protect the service; a request can then wait before it starts — see [Terms of Service, section 2](/legal/terms-of-service#2-access-and-accounts).

## Request size

| Limit | Value | Over it |
| - | - | - |
| Request body | 200 MiB | `413 request_too_large` |
| Body upload time | 55 seconds | `408 request_timeout` |

Image limits are on [Image input](/docs/images#accepted-images). An image sent as a data URL counts toward the request body.

## How long a request may run

A request can run for up to 60 minutes. After that a non-streaming request returns `504 upstream_timeout`; a stream ends with an `upstream_error` event — see [Streaming](/docs/streaming#errors-during-a-stream).

## Model limits

The context window and the max output depend on the model — see [Models](/docs/models).


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