---
title: "Rate Limits & Quota"
description: "NexLev API usage is metered by quota — a per-request cost deducted from your plan's balance — rather than a flat requests-per-second limit."
source: "https://dashboard.nexlev.io/docs/api/rate-limits"
---

# Rate Limits & Quota

NexLev API usage is metered by **quota** — a per-request cost deducted from your plan's balance — rather than a flat requests-per-second limit.

## How Quota Works

- Every successful request deducts a fixed amount of quota, shown as 🥞 on each endpoint's reference page (e.g. [Channel Analytics](/docs/api/channel-analytics)).
- Quota resets according to your plan's billing cycle.
- Cached results (where noted on an endpoint's reference page) do not count against quota.
- Failed requests (4xx/5xx) are not charged.

## Monitoring Usage

Check your remaining quota anytime at [Manage API Key](https://dashboard.nexlev.io/nexlev-api/manage-api-key).

## Exceeding Quota

Once your quota is exhausted, requests receive a `429` response:

```json
{
  "error": "Quota Exceeded",
  "details": "You have exceeded your API quota. Please try again later."
}
```

> **Tip**
>
> Cache responses where possible and batch requests to avoid burning through
> quota on redundant calls — most endpoints' reference pages call this out under
> "Best Practices."

## Per-Endpoint Hourly Limits

Some asynchronous, job-based endpoints additionally enforce an hourly request cap independent of quota. These are documented on the relevant endpoint's reference page — for example, [Channel Analysis](/docs/api/channel-analysis#create-channel-analysis-job) allows 100 job creations and 500 result fetches per hour per API key.