Manage team API keys and budgets by project

Assign keys to clear owners

Avoid sharing one production key across team members, services and test environments. Use a distinct enterprise key for each project or agent, with a named owner, permitted models and spending limits. RelayAI associates an enterprise agent through its bound key; callers cannot claim another agent identity.

Configure access and budgets together

An agent model allowlist and the API key's model access both apply. Enterprise, department, project, agent and key budgets can have thresholds and over-limit actions. Test the expected alert or block with a real request before relying on the setting.

Review regularly

Inspect unused keys, model access, request origins and measured usage. Revoke a key when its owner leaves or its project ends. Model API governance does not automatically control a local shell, files or browser; those tools need their own integration.