Operations
Production integration
The API v1 contract is synchronous and file-based. Production clients should bound retries, preserve request IDs, monitor their own latency and error rates, and protect the available balance.
Limits and latency
- File size
- 30 MB
- Audio duration
- 60 minutes
- Billing minimum
- 1 second
- Suggested short-file timeout
- 120 seconds
End-to-end latency depends on audio duration, selected task, model, and current capacity. PAYG does not include a contractual p95 latency or concurrency allocation. Measure representative files and contact oruk before a high-concurrency launch.
Retry policy
| HTTP status | Action | Notes |
|---|---|---|
| 400, 401, 402, 404, 413, 422 | Do not retry automatically | Fix the request, credential, balance, or file. |
| 409 | Do not create a new chargeable request blindly | The request ID has already been used. Reconcile against usage history. |
| 429 | Retry | Exponential backoff with jitter. Reduce concurrency if it persists. |
| 500, 502, 503, 504 | Retry | Use the same logical request ID and a bounded retry budget. |
Observability
- Log your X-Request-ID and returned result ID.
- Track status code, duration, model, task, and client-perceived latency.
- Alert on sustained 429 or 5xx rates, not isolated retries.
- Compare application records with the request-level usage ledger.
- Monitor balance and enable threshold email alerts or auto-recharge.
- Never log bearer keys, audio content, or complete API responses by default.
Launch checklist
- 01Keep keys in a server-side secret manager.
- 02Use one key per environment and rotate it on exposure.
- 03Validate representative audio, microphones, accents, and edge cases.
- 04Set timeout and retry budgets explicitly.
- 05Load test below an agreed production concurrency envelope.
- 06Add balance alerts and a payment method before launch.
- 07Review the security, privacy, and responsible-use commitments.
- 08Define a human escalation path for consequential emotion use.