Teams

Control shared keys, budgets, and limits

One workspace for the whole organisation: isolate spend, constrain access, and see where credits actually go.

Teams

Issue independent API keys for every service, environment, and customer. Rotate or revoke one without affecting the rest.

Attach a monthly cap to a key. When it is reached, requests return 402 rather than silently spending.

Restrict keys to specific modalities or model families, so a front-end key cannot reach your billing surface.

Break spend down by key, model, modality, and time window. Export to CSV or read it through the API.

Invite engineers with roles that separate billing access from key provisioning.

Every management action is recorded with the acting key, target, timestamp, and source address.

Teams

Need a security review pack?

We can share our architecture summary, data-flow diagram, and retention policy.

Provision programmatically

A management key can mint scoped standard keys, so onboarding a customer does not require a human in the dashboard.

Separate credential classes

Management keys cannot generate work, and generation keys cannot manage keys. A leak is contained either way.

Enterprise terms

Custom rate limits, invoicing, SSO, a private networking option, and a contractual uptime SLA.

Start with one workspace, then add keys, budgets, and seats as adoption grows.