Control shared keys, budgets, and limits
One workspace for the whole organisation: isolate spend, constrain access, and see where credits actually go.
Teams
Control shared keys, budgets, and limits
Keys per workload
Issue independent API keys for every service, environment, and customer. Rotate or revoke one without affecting the rest.
Budgets as hard stops
Attach a spending cap to a key. When it is reached, requests return 402 rather than silently spending.
Scoped permissions
Restrict keys to specific modalities or model families, so a front-end key cannot reach your billing surface.
Usage history
Review requests and charges by model, key, and time window in the workspace dashboard.
Member access
Invite members to a workspace and manage their roles from the dashboard.
Workspace files
Browse generated images and videos, download results, and remove files before automatic expiry.
Teams
Need a security review pack?
We can share our architecture summary, data-flow diagram, and retention policy.
Take CAPI across your organization
Start with one workspace, then add keys, budgets, and seats as adoption grows.