Skip to Content
Getting startedGetting started

Getting started

Four steps, using only a browser and one command. For team setup and quotas, see the enterprise console.

Audience: members and administrators. You only need an account that can sign in.

1. Get access

RouteAddressNotes
You received an invitationThe /join/<token> page in the linkSent by your enterprise administrator. See Accepting an invitation
Self-service registrationalltokens.si/enterprise-register Creates a new enterprise and makes you its owner. The platform may require review

Whether registration is open, and whether it requires approval, is a platform setting — the page shows the current state. If you are joining an existing team, do not use the registration form: it creates a separate enterprise rather than adding you to your colleagues’.

2. Sign in

Sign in at alltokens.si/sign-in .

3. Where your key comes from

This is the part people get wrong, because there are two kinds of key and they are billed differently:

Key typeCreated inSpends
Personal keyConsole → API keysYour own account balance
Enterprise shared keyConsole → Shared API keysThe enterprise shared balance, with no fallback to your personal wallet

Members usually do not hold a shared key (administrators create and hand those out), so the key you are given is normally a personal one. The request format is identical; only the key and the billing attribution differ. See Keys and authentication.

4. Make your first request

The API is OpenAI-compatible. Base URL:

https://alltokens.si/v1
curl https://alltokens.si/v1/chat/completions \ -H "Authorization: Bearer sk-..." \ -H "Content-Type: application/json" \ -d '{ "model": "replace with a model the platform actually serves", "messages": [{"role": "user", "content": "Hello"}] }'

Model names are whatever the platform currently serves. These docs do not list them — availability and pricing change. Check the models and pricing  page and substitute a real name.

Confirming it worked

  • The request returns 200 with choices in the body.
  • The call shows up under Usage or Request logs.

For 401 / 402 / 403 / 429, see the FAQ.

Next