Getting started

Everything below happens in the console (console.seligo.cloud) until the final step, where you copy a curl command and make your first API call.

1. Create your org

Sign up at the console. Signup creates a Seligo org — your team’s isolation boundary. Billing, API keys, and usage all hang off this org. Invite colleagues as members so each principal has their own identity (and, later, their own private-GPU entitlements).

Org & user identity matter for private GPUs: a GPU burst is requested by a user and billed to their org. Each member gets their own live-burst cap, and private-GPU offerings are enabled per-org by staff. See the Private GPU page.

2. Top up your balance

Go to Billing in the console and add funds. All usage is metered and billed in EUR. Run out of balance and requests fail closed until you top up.

3. Create an API key

In the console Keys page, create a key. It will look like rk-…. Keep it secret — it authenticates every API call and never appears in our logs or usage events.

Keys are the credential for both public models and private-GPU self-serve (start/stop) endpoints. A single key scopes everything to your org + user.

4. Make your first request

List what’s available, then call a catalogue model:

export SELIGO_BASE="https://api.seligo.cloud/v1"

# what can I call?  (public catalogue)
curl -s "$SELIGO_BASE/models" \
  -H "authorization: Bearer rk-…"
# first chat completion — pick a model id from /v1/models
curl -s "$SELIGO_BASE/chat/completions" \
  -H "authorization: Bearer rk-…" \
  -H "content-type: application/json" \
  -d '{"model":"scaleway/Meta-Llama-3-1-8B-Instruct",
       "messages":[{"role":"user","content":"Hello"}]}'

5. See your usage

Back in the console Usage page, your calls are metered with cost in EUR, per model and per key. Streaming requests are metered on completion using the streamed token counts.

Next: read the full API reference, or jump straight to private GPU access.