VIUCraft splits its URLs by base path. Knowing the split tells you, at a glance, which host and prefix any operation lives under.
Rule of thumb: upload and delivery live at the root; everything else (management, CRUD, discovery) lives under /api/.
All paths below are relative to your tenant host, https:// (free tier: https://viucraft.com/free/acc_ for delivery). See Tenancy & URL Bases.
Root — upload & delivery
| Purpose | Method + path |
|---|---|
| Upload | POST /upload (alias: POST /api/upload) |
| Deliver / transform | GET / |
| Deliver original | GET / |
These are the high-traffic, public-facing paths. Delivery is a plain GET of an image URL — see Delivery & Transform URL Grammar.
/api/ — image & account management
| Purpose | Method + path |
|---|---|
| List images | GET /api/images |
| Image metadata | GET /api/images/ |
| Update (move) image | PATCH /api/images/ |
| Delete image | DELETE /api/images/ → 204 |
| Bulk upload | POST /api/upload/bulk |
| Export images (zip) | POST /api/images/export |
| Folders | GET /api/folders, POST /api/folders/move |
| Cache | POST /api/cache/purge, POST /api/cache/warm |
| Capabilities | GET /api/capabilities |
| OpenAPI spec | GET /api/openapi.json, GET /api/openapi.yaml |
/api/v1/ — versioned services
| Purpose | Method + path |
|---|---|
| Unified discovery (recommended) | GET /api/v1/whoami |
| Account config | GET /api/v1/account |
| Usage | GET /api/v1/usage |
| Batch jobs | POST /api/v1/jobs, GET /api/v1/jobs/ (+ GET /api/v1/jobs/ SSE) |
| Webhooks | POST /api/webhooks, GET/DELETE /api/webhooks/, POST /api/webhooks/ |
| Presets | GET/POST /api/v1/presets, GET/DELETE /api/v1/presets/ |
/api/v1/cli/ — CLI client endpoints
| Purpose | Method + path |
|---|---|
| Validate key | POST /api/v1/cli/auth |
| Identity + usage | GET /api/v1/cli/whoami |
| CLI image ops | GET/POST /api/v1/cli/images... |
/mcp — agent (Model Context Protocol)
| Purpose | Method + path |
|---|---|
| MCP server (agents) | POST /mcp — authenticated with Authorization: Bearer vc_live_... |
Note the auth difference: REST endpoints use the X-API-Key header; the MCP endpoint uses Authorization: Bearer.
Discovery first
If you only have an API key, start with GET /api/v1/whoami — it returns your identity, URL bases, usage, and full capabilities in one call, so you can bootstrap without hard-coding anything. The complete request/response contract for every endpoint above is in the OpenAPI spec.