There is no public API yet.
We would rather tell you that on the first line than let you read a page of endpoint documentation and discover it at the sign-up form. Nothing below is callable today.
Not in development, not in preview, not behind a waitlist you can jump. It is a real intention with no date attached.
An API is a promise you cannot quietly withdraw.
Three things have to be true before a key we hand out can spend your balance.
Spend has to be safe first
Generation costs real money per run. An API key that can spend your balance needs limits, quotes and a settlement path we would stake our own money on. That work is not finished.
The model catalogue has to be stable
An endpoint that returns models is a contract. Publishing one before the catalogue settles means breaking it, and breaking an API is worse than not shipping one.
Agents need a boundary
Agent Ora acts behind human approval. Exposing that over an API without the same guarantee would quietly remove the guardrail that makes it trustworthy.
What we expect it to look like.
Useful if you are deciding whether it is worth waiting for. Treat it as direction, not documentation. Paths, payloads and names will change, and none of these respond today.
| Method | Path | Intent | Status |
|---|---|---|---|
| POST | /v1/generate/image | Create images with any catalogue model | Not live |
| POST | /v1/generate/video | Video generation with queue + webhook | Not live |
| GET | /v1/jobs/:id | Poll job status and outputs | Not live |
| GET | /v1/models | List models, costs and capabilities | Not live |
| POST | /v1/agent/run | Run an Agent Ora task with guardrails | Not live |
No sandbox, no test key, no staging host. There is nothing to point a client at, and we are not going to publish one that returns fixtures and call it an API.