---
title: "limit_exceeded — subscription usage limit exceeded"
url: https://lumean.app/es/developers/docs/errors/limit-exceeded
locale: es
description: "The third of the five 429 sources. The body has only `message` and `reason` — neither the token quota fields (`window`/`limit`/`used`) nor a `Retry-After` header."
generated: 2026-10-17
---

# limit_exceeded — subscription usage limit exceeded

- HTTP: `429`

- `reason`: `limit_exceeded`

- Encabezado `Retry-After`: no

## Qué pasó

The third of the five 429 sources. The body has only `message` and `reason` — neither the token quota fields (`window`/`limit`/`used`) nor a `Retry-After` header.

## Por qué

The limit belongs to the subscription, not the key: it caps account consumption over the billing period of the plan. Switching keys will not help here — all keys on the account hit the same counter.

## Qué hacer

Telling it apart from the token quota is simple: that one has `Retry-After` and window numbers; this one has nothing. Backoff will not help until the period ends: you need to wait for `period_end`, not "a couple of minutes". The quick ways out are a different plan or an add-on package.

## Siguiente petición

`GET /usage` — the limit entries have `period_start`, `period_end`, and `resets_in`; they show how long to wait. For a specific service — `GET /usage/{service}`.

## Relacionado

- [Guide: limits and the 429 code](https://lumean.app/es/developers/docs/guide/limits)
- [token_quota_exceeded — key limit, not subscription limit](https://lumean.app/es/developers/docs/errors/token-quota-exceeded)
- [GET /usage](https://lumean.app/es/developers/docs/api/get-usage)
- [GET /usage/{service}](https://lumean.app/es/developers/docs/api/get-usage-service)
- [Account limits](https://lumean.app/es/limits)
- [Change plan](https://lumean.app/es/shop)

---

- Esta página en el navegador: https://lumean.app/es/developers/docs/errors/limit-exceeded
- Referencia completa legible por máquina: https://api.lumean.app/docs/llm.md