Get started
Quickstart
Authenticate, ship your first workload, and watch it come up. Every call carries your per-workspace key — send it as x-api-key (or Authorization: Bearer).
1
Mint an API key
Grab a key from your workspace's API keys page in the console. It looks like llc_… and is shown once. Verify it by asking which workspace it belongs to.
shell
export LIVELLM_KEY="llc_..."
# Which workspace does this key belong to?
curl https://api.live-llm.com/v1/me/tenant \
-H "x-api-key: $LIVELLM_KEY"
# => { "name": "acme", "plan": "...", "spec": { "workloads": [...] } }2
Create a workload
Each resource is a workload; create uses a per-type endpoint because a VM body differs from a container-app body. There is no workspace name in the path — your key already identifies it. Ship an nginx container app — the create returns 202 and provisioning starts immediately.
create.sh
curl -X POST https://api.live-llm.com/v1/me/tenant/workloads/pod \
-H "x-api-key: $LIVELLM_KEY" \
-H "Content-Type: application/json" \
-d '{ "id": "web", "image": "nginx:1.27",
"ports": [{ "name": "http", "port": 80 }] }'
# => 202 Accepted — the workload is being reconciled.3
Poll status until it's running
Watch the live status until the workload reaches its running phase. The HTTP port becomes a public hostname at web-80-acme.cloud.live-llm.com.
poll.sh
curl https://api.live-llm.com/v1/me/tenant/status \ -H "x-api-key: $LIVELLM_KEY" # ...then open your app (the status lists each port's public URL): curl -I https://web-80-<workspace>.cloud.live-llm.com