How do I give every developer their own API key with a monthly budget, and revoke it when they leave?
Use a hosted gateway with a company workspace. On Standard Compute every developer you invite gets their own key with its own plan and monthly compute budget ($19 to $249 a month), and at that budget the key gets HTTP 402 while everyone else keeps working. The router sends each step to the cheapest model that can do it, so the budget lasts. When someone leaves, an admin removes them: their keys are revoked at once, their plan stops renewing and the audit log records it.
How it works on Standard Compute
- Create a company workspace and invite each developer by email. Setup and invitations are free.
- Each invite comes with the developer's own key. Pick a plan per key, for example Economy at $39 with $39 of compute or Standard at $89 with $89, and an admin approves and pays.
- The agent changes only its base URL to https://api.stdcmpt.com/v1 and uses the key. Claude Code, Codex CLI, Cline and other OpenAI- or Anthropic-compatible agents work.
- At the key's monthly budget, new requests get HTTP 402
budget_exhausteduntil the plan renews or an admin moves the key to a bigger plan. Keys on Pay as you go draw from a prepaid company balance at usage plus 7.5%, with a monthly limit per key and for the whole company. - When someone leaves, an admin removes them from the workspace. The keys they hold as a member are revoked immediately, their plan is set not to renew, and the removal shows in the audit log (Enterprise, or $199 a month as an add-on).
- Shared services get Admin-managed keys that belong to the company, so nothing breaks when a person leaves. Any key can be rotated or revoked on its own.
Hosted gateways with a budget per developer key
| Gateway | Budget per key | At the limit | SSO and admin controls |
|---|---|---|---|
| Standard Compute | A plan per key with its own monthly compute budget; Pay-as-you-go limits per key and per company | HTTP 402; other keys keep working | Roles, Admin-managed keys and removal that revokes keys; audit log $199/month and SSO (SAML) $399/month as add-ons, or Enterprise at $1,499 |
| Requesty | Monthly cap per key; group budgets on Enterprise | HTTP 412 at a key's cap | SSO and audit logs on Enterprise |
| Vercel AI Gateway | Budgets at four scopes | HTTP 402, described as a soft cap | SAML SSO, SCIM and audit logs on Vercel Enterprise |
| Portkey | Key and workspace budgets on Enterprise and select Pro | Enforced at the budget | SSO and SCIM on Enterprise |
| OpenRouter | Credit limit per key with a reset period | HTTP 402 at a key's credit limit | SSO/SAML on Enterprise |
| LiteLLM, self-hosted | Virtual-key budgets, with its database | Budget error before the provider call | SSO free for up to 5 users; more on its Enterprise license. You run the proxy |
Other gateways from each vendor's own pages, checked October 14, 2026 (sources on our production gateway comparison). Standard Compute is our product.
When another option fits better
- You want to pay list price per token with no monthly plan: Vercel AI Gateway or OpenRouter, with a credit limit per key.
- Keys and prompts must stay inside your own infrastructure: self-hosted LiteLLM.
- You bring your own provider keys: we don't support BYOK.
- Procurement needs a SOC 2 report today: we don't have one yet.
Where Standard Compute fits
A key per developer with its own plan, a router that spends each budget on efficient models, and offboarding that revokes keys in one step. Opt-in Europe or US rules apply per company, team or key, and we don't train on your prompts or store them.
FAQ
How do I give every developer on my team their own API key for coding agents with a monthly budget cap, and revoke it the day someone leaves, without building a proxy?
Use a hosted company workspace. On Standard Compute each invited developer gets their own key with its own plan and monthly compute budget, and at that budget the key stops with HTTP 402 without touching anyone else. When someone leaves, an admin removes them: their member keys are revoked at once, their plan stops renewing and the audit log records it. Agents only change their base URL, so there is nothing to host.
Can I see what each developer spends?
Yes. Each key has its own usage view and request log, with the model that served each request and its latency, never the prompt text. Admins see every company key.
What if a developer needs more than their plan's budget this month?
An admin can move the key to a bigger plan, prorated, or put it on Pay as you go at usage plus 7.5% with a monthly limit for that key.
Can developers sign in with our identity provider instead of personal emails?
Yes, with SSO (SAML), part of Enterprise or $399 a month on its own. People on your verified company domain join the workspace automatically. SCIM provisioning is on request.
Does a key for a shared CI service stop working when its creator leaves?
Not if it is an Admin-managed key. Those belong to the company rather than a person, and removing a member only revokes the keys that member holds.