The API: the same develop, started from your own system
A develop you start from your own service is the develop a director starts in the studio: same routes, same ledger, same frames. Submit the job, take the id, and listen.
- One URL describes the whole surface as OpenAPI 3.1, and every route ships with a runnable request that CI checks. A route nobody can call is a promise nobody can keep.
- Long work does not block. Submit, take the job id, and listen. The socket is addressed to your organization, not to a seat, so a run one person started is watchable from another.
- Tokens are held before anything is queued, settled when the frame lands and released when it fails. An interrupted develop costs nothing.
- A purchase becomes yours when the payment webhook lands, never when the browser comes back.
- An organization key opens every route your session opens, and POST /api/mcp gives an agent six tools that commission a develop from asset ids. A key cannot spend money or invite a seat — that stays with a person. Outbound webhooks are still designed and not built, and the docs say which is which.