Live status
Current availability and incident history are published on our status page. The link is added to the navbar once the status page is live.Reliability behavior you can rely on
- Fail-closed billing. If a dependency is unavailable, a billable call returns a
503rather than silently running for free, so you are never charged for an incomplete result. Retry with backoff. - Idempotent creates. Retries with the same
Idempotency-Keydo not duplicate work or double-charge. - Instant revocation. A revoked key stops working immediately.
Retries and timeouts
- Retry
429and5xxwith exponential backoff (see Errors). - Generation and edits are AI-backed and can take several seconds. Set a generous client timeout. The SDKs and MCP server default to 450 seconds, which sits deliberately above the server-side limits so a slow generation is never abandoned by the client while the server is still working on it.
Formal uptime targets and the enterprise SLA are published here as they are finalized.