Status · public beta

API Many status

Last reviewed August 30, 2026.

This page is the policy fallback, not the independent monitor. Open status.apimany.com for live gateway checks and the customer-facing service and model availability. That status service is designed to run in a separate failure domain.

Current beta surface

The API includes GET /v1/models, streaming POST /v1/chat/completions, POST /v1/messages, POST /v1/responses, embeddings and transcription, and asynchronous media at /v1/images/generations, /v1/videos/generations and /v1/music/generations with GET /v1/tasks/{id}. The website, billing, sign-in, generation and content downloads can have independent availability.

How to check model availability

Call GET /v1/models with your API key to list enabled models, their supported output specification and current customer rates. The response is a stable access catalog, not an instantaneous availability guarantee. Check status.apimany.com for best-effort health. The larger website catalog includes research and planned models; it does not mean that every model is callable. Examples in the documentation are usable only when returned by model discovery.

No SLA during public beta

We do not promise uptime, latency, support response time, advance maintenance notice, recovery time, or permanent access to a model during public beta. Health checks can identify some failures, but cannot guarantee that a request will succeed. A healthy discovery endpoint does not prove generation or downloads are healthy.

Uncertain requests

A timeout or disconnected response does not prove that work was rejected. A request can remain reserved for reconciliation instead of being automatically submitted again. Media jobs require an Idempotency-Key; repeating the same key and payload returns the original job. Poll its API Many job ID rather than submitting new keys. A reconciliation_required job needs review, not a replacement submission.

Media result retention

A successful image or video is downloadable for 24 hours after its completed_at timestamp, using the owner’s active API key. After expiry the content endpoint returns 404, even if the job receipt still says succeeded. An expired result is not a service outage. Download and save completed results promptly.

Report a problem

Email [email protected] with the request ID, model ID, approximate UTC time, status code, and error code. Never send your API key or sensitive prompt content. Confirmed incident information may be added here when public disclosure is appropriate, but no update interval is promised.