API
API Reference
Everything Seyu does in the studio, your systems can do over HTTPS. One resource, four verbs, realms as a service.
Authentication
All requests are authenticated with an API key, sent as a bearer token. Keys are created in your dashboard and scoped per workspace.
zsh
curl https://api.seyu.app/v1/realms \ -H "Authorization: Bearer $SEYU_API_KEY"
Endpoints
| Method | Path | Description |
|---|---|---|
| POST | /v1/realms | Create a realm from a brief |
| GET | /v1/realms/:id | Fetch a realm and its status |
| POST | /v1/realms/:id/notes | Give a directing note |
| POST | /v1/realms/:id/ship | Ship the realm to a domain |
Create a realm
Send a brief and a model. The realm starts drafting immediately, and the response returns its id and status.
POST /v1/realms
curl https://api.seyu.app/v1/realms \
-H "Authorization: Bearer $SEYU_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "seyu-apollo",
"brief": "a cinematic launch site for a Swiss
watch brand. midnight mood, engraved
serif, one spotlight."
}'response
{
"id": "realm_8f3k2p",
"status": "drafting",
"model": "seyu-apollo",
"preview_url": "https://realm-8f3k2p.seyu.app"
}Direct a realm
Notes work exactly like director mode in the studio: plain language in, applied changes out.
POST /v1/realms/:id/notes
curl https://api.seyu.app/v1/realms/realm_8f3k2p/notes \
-H "Authorization: Bearer $SEYU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "note": "slower entrance, more suspense" }'Ship a realm
POST /v1/realms/:id/ship
curl https://api.seyu.app/v1/realms/realm_8f3k2p/ship \
-H "Authorization: Bearer $SEYU_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "domain": "aurelia.watch" }'Ships are atomic and versioned. Shipping again replaces the live version, and rolling back is a single call with a previous version id.
Pre-season
The API opens together with the platform at launch. Endpoints and shapes documented here describe the launch surface and may be refined until then.