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

# Rate Limits

> Understand CREAO Developer API account and IP rate limits.

## Account limits

Developer API traffic is rate-limited by CREAO account. The active account run limit is shown in Developer Console on the dashboard.

Limits are applied before execution starts. If a create-run request is rejected by rate limiting, no run is accepted.

Agent create, replacement update, and natural-language edit creation requests also have a narrower write limiter: 30 writes per account per hour. If a write is rejected by this limiter, no agent row is created or changed and no edit run is accepted.

## IP limits

Developer Platform also applies an IP-level safety limit to protect the service from abusive traffic. This limit applies before account-specific routing.

## Handling `429`

When you receive `RATE_LIMITED`, wait for the `Retry-After` header before retrying when the header is present.

```http theme={null}
HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json

{ "error": "RATE_LIMITED" }
```

Use exponential backoff with jitter for repeated retries. Do not retry non-idempotent run creation in a tight loop; each accepted run can consume credits.

## No per-key tuning in v1

Developer Platform v1 does not expose per-key, per-agent, per-project, or per-end-user rate-limit configuration. Limits apply at the account level.