Errors and usage limits - OutReign Developers

Read the status and body

Parse the JSON body as well as the HTTP status. Responses may contain an error even when an upstream operation was handled without a transport failure.

Status	Meaning / action
`400`	Check the request body and required fields.
`401`	Check the API key, or reconnect an MCP OAuth session.
`403`	Check plan access or another authorization restriction.
`404`	Check the endpoint and that the resource belongs to the account.
`410`	The legacy workflows endpoint is retired.
`429`	Pause requests; the current usage allowance has been reached.
`500`	The operation failed; inspect the error and avoid immediate write retries.

Rate-limit headers

REST responses that pass the rate check include X-RateLimit-Remaining and X-RateLimit-Reset. Rate-limit rejections also include these headers. Read them when present; early authentication failures may not include them.

Plan	Requests per minute	Requests per day
Explore	No API/MCP access	No API/MCP access
Starter	30	2,000
Growth	60	10,000
Pro	120	50,000
Agency	300	200,000

REST daily usage is shared across the owner’s API keys; its short-window buckets are per key and resource. MCP checks its own per-user call allowance. API request allowance, MCP call allowance and feature-specific credits are not interchangeable balances. Check your current allowance in OutReign and on the pricing page.

Retry safely

Back off after rate-limit and transient service errors.
Do not automatically retry authentication failures with the same invalid credential.
Do not assume write requests are idempotent. After an ambiguous timeout, read the resource back before repeating a create, import or other write.
Avoid running enrichment or generation repeatedly just to poll progress; these operations may consume allowance.

No public idempotency-key contract is documented for the REST API. Implement reconciliation in your integration rather than assuming duplicate writes will be ignored.

⌘I