API documentation

Three surfaces, three key scopes. Pick the one that matches the client you already have — do not point tools at raw GPU worker ports.

/v1 — OpenAI Chat Completions shape (chat-scoped key): text, vision image_url (data URI or SSRF-safe https), PDF text / embedded-image vision, opt-in web search
/comfy — ComfyUI HTTP protocol (comfy-scoped key): upload → LoadImage → img2img/edit graphs, plus POST /api/comfy/compose for generate/edit helpers
/api/jobs — studio image/video cards (images-scoped key)

Authentication

Every programmatic call needs Authorization: Bearer <key>. Keys are issued on your account page and shown once. Scopes do not mix: a chat key cannot call /comfy; a comfy key cannot call /v1.

HTTP Basic is accepted on /comfy only: API key as username, empty password — for OSS tools that can only carry credentials in the URL.

What never comes off

Child-safety floors run on every surface, on every build, with no tenant switch. See what we block. Commercial builds also compile adult categories out of the allowable set.

Quick checks

# List chat models
curl -sS https://YOUR-HOST/v1/models \
  -H "Authorization: Bearer YOUR_CHAT_KEY"

# List Comfy checkpoints (via object_info)
curl -sS https://YOUR-HOST/comfy/object_info/CheckpointLoaderSimple \
  -H "Authorization: Bearer YOUR_COMFY_KEY"

# List studio cards
curl -sS https://YOUR-HOST/api/meta \
  -H "Authorization: Bearer YOUR_IMAGES_KEY"