Skip to main content

Account limits

CREAO CLI traffic is rate-limited by CREAO account. The active account run limit is shown in Developer Console on the dashboard. Default limits are 30 requests per account per minute across /v1/*, plus 30 writes per account per hour for agent, product-profile, workspace, secret, and skill writes. Create-run requests (POST /v1/runs, POST /v1/realtime/runs, POST /v1/super-agent/runs, POST /v1/super-agent/realtime/runs) share that per-minute budget unless CREAO has set a stored per-account override with separate read / write / run budgets. Creating or replacing an agent from a bundle is one write, however many files the bundle holds. Limits are applied before execution starts. If a create-run request is rejected by rate limiting, no run is accepted. Room posts (POST /v1/rooms/{room_id}/messages) have their own limits on top of the per-minute budget: 60 posts per minute per account, and 30 posts per hour per account in each room unless the post sets trigger_agents: false. An account can also hold at most 10 room event streams open at once, across all rooms; one more returns 429 with Retry-After. See Rooms. If a write is rejected by an hourly write limiter, no agent row is created or changed, no edit run is accepted, no workspace file is uploaded or deleted, no skill is installed or toggled, and the product profile is not replaced.

IP limits

CREAO CLI 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.
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

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