Rate Limits

Expect throttling

APIMUX enforces rate and quota controls. Build retry behavior into your client instead of assuming unlimited parallelism.

Recommended client behavior

• Retry only when the failure is transient
• Use exponential backoff with jitter
• Avoid retry storms from many workers sharing one API key
• Prefer capability discovery up front instead of repeated trial-and-error calls

CLI and agent workflows

When the CLI is used inside scripts or agents, treat 429 and upstream temporary failures as recoverable conditions. Keep retries bounded and surface the final failure clearly if the request still cannot complete.

Reference

For the current protocol surface and auth scheme, use the generated API reference at /settings/api-docs.