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

# Automation limits

# Automation limits & billing

Automations use the [Agent API](../api-reference/agent) with `X-Agent-Id` and `X-Api-Key`. Besides validation and [rate limits](../api-reference/agent#rate-limits), your workspace may be subject to **plan or subscription limits** on how many **new approvals** you can create.

## Approval quota (`USAGE_APPROVAL_LIMIT`)

When **billing and usage limits** are enabled for your deployment, creating an approval can fail with:

| HTTP    | Body (typical)                                                                            |
| ------- | ----------------------------------------------------------------------------------------- |
| **403** | `{ "error": "USAGE_APPROVAL_LIMIT", "code": "USAGE_APPROVAL_LIMIT", "over_limit": true }` |

This comes from the server when the team is **over the current plan’s approval allowance** for the active billing period (enforced when the approval is created).

### What integrators should do

* Treat **403** `USAGE_APPROVAL_LIMIT` as a **business / capacity** error, not a bug: log it, notify operators, and **avoid tight retry loops** on create.
* **Queue or defer** new approvals until the workspace owner resolves billing (upgrade plan, wait for the next period, or adjust usage—depending on how your deployment defines plans).

### What workspace owners see

When **Billing** is available in the [web dashboard](./web-dashboard), owners can review **plans**, **usage**, and upgrade or change subscription there. Members and automations cannot fix quota errors without an owner (or your operator) adjusting the subscription or plan.

## Related

* [Agent API: errors](../api-reference/agent#error-responses)
* [API overview: typical errors](../api-reference/overview#agent-authentication)
* [Credentials](./credentials)