Title: Fair usage policy
Source: https://nodely.io/docs/free/policy/

# Fair usage policy

New free tier limits from 1 January 2027

The free tier limits on this page start on 1 January 2027 (00:00 UTC). Until then the free tier keeps 200k requests or 5 GB a day per IP and site and 60 req/s per IP, with no separate limit for bot traffic, and MainNet time travel stays free.

<a id="general"></a>

## General

-   Node & Indexer APIs are FREE!
-   No tokens, no setup, no surprises
-   Free tier provides vanilla flavor API only - so you can easily migrate to your own
-   [Time travel](https://nodely.io/docs/access/time-travel/) (state at past rounds) is free on testnet; mainnet history needs a paid plan
-   Please mention using Nodely on your project site when doing > 1M requests monthly
-   Both front-end & back-end traffic is subject to daily quota restrictions.
-   IPFS gateway traffic is counted towards daily quota along with all other APIs
-   Need more? The [Boost and Unlimited plans](https://nodely.io/docs/access/) add API tokens, usage analytics and higher request rates; Unlimited also drops the daily quota.

Tip

Public good projects can apply for ability to go above free tier.  
See [public goods projects tier](https://nodely.io/docs/unlimited/public-goods-projects).

<a id="free-tier-limits"></a>

## Free tier limits

Please observe the following limits. Nodely reserves the right to start rejecting requests once daily quota is exceeded.  
Projects can can check the [dashboard](https://g.nodely.io/d/nodelyapi/) to see the quota status.

Daily quotas count per UTC day and reset at 00:00 UTC.

<a id="per-project--site"></a>

### Per project / site

-   Up to 128k requests per day (about 3.8M per month)
-   1000 requests/s per site across all free tier regions
-   2 GB worth of responses per day (about 60 GB per month)

<a id="per-individual-user--browser-ext-ip-address"></a>

### Per individual user / browser (ext. IP address)

-   30 requests/s, 10 concurrent calls
-   5 requests/s for bot traffic: requests without a browser `Referer` or `Origin` (backends, scripts, bots)
-   18 transaction POSTs per second
-   128k requests or 2 GB worth of responses per day

Caution

-   Free endpoints add artificial 150ms (250ms for archival) delay for requests.
-   Doing above 1MM requests monthly ? Mention Nodely on your project site.

<a id="exceeding-limits"></a>

### Exceeding limits

<a id="realtime-requests"></a>

#### Realtime requests

For requests that exceed per second or concurrency limits the API will return HTTP 429 code. Please use exponential backoff after receiving 429 response.

<a id="daily-quotas"></a>

#### Daily quotas

API edges refresh quota usage about every 30 seconds, from usage data that runs a few minutes behind. As an IP address or a site gets close to its daily quota, a growing share of its requests is rejected at random. Once the quota is used up, all of them are rejected until 00:00 UTC.

You can expect :

| HTTP result | when |
| --- | --- |
| 429 | you exceeded number of requests/s |
| 429 | you exceeded number of requests in flight |
| 403 `Daily free API quota exceeded` | you are close to or over the daily byte or request quota |

Caution

Failed requests count as requests towards quota

See [quotas and rate limits](https://nodely.io/docs/access/limits/) for the paid plans.