Projects, tenants & users
The identity model, plus your API keys and scopes.
Three identities frame every Stacklink call. (The fourth — the session — has its own page.)
The identities
| Noun | What it is | Who creates it |
|---|---|---|
| Project (consumer app) | Your application's account on Stacklink. Holds API keys, enabled providers, auth configs, and billing. | You, once. |
| Tenant | One of your end-customers (a business). Owns connected accounts and triggers. | Implicitly, on first session. |
| User | A person inside a tenant. Used for attribution and per-user context. | Implicitly, on first session. |
A session then scopes a working context for one tenant/user.
API keys & scopes
Every /v1/* call authenticates with Authorization: Bearer <key> (or x-stacklink-key). Keys carry
scopes that gate what they can do — for example sessions:create, tools:execute,
connections:manage, knowledge:read, triggers:manage, logs:read. Project registration and a few
admin operations use a separate x-stacklink-registration-key instead.
See the scopes reference for the full list.
✦ 30-day trial
2 projects during the trial
The trial includes 2 projects sharing 100,000 tool calls and the separate resource allowances listed in Billing & usage.
Start free trial→No card required. Nothing charged automatically.