Overview
Enterprise controls for organizations, projects, roles, security, SSO, webhooks, notifications, and usage separation.
This section describes the enterprise product layer built on top of the core API platform. It is where customer governance starts to matter: who can use which models, which keys belong to which team, and how usage is separated across projects.
Main concepts
| Concept | What it controls |
|---|---|
| Organizations | Top-level membership, policy, billing, and security boundaries |
| Projects | Team, environment, workload, key, and usage separation inside an organization |
| Member roles | Who can manage organization settings, project resources, billing, and security |
| Team API keys | Which people or systems can call public API routes for a project or workload |
| Security policies | SSO, session behavior, key restrictions, and access controls |
| Billing and finance workflows | Plan ownership, invoices, renewal contacts, and spend visibility |
| Operational webhooks | System-to-system event delivery for usage, billing, member, key, and security events |
Best use
This section is most useful for:
- platform admins
- engineering managers
- security owners
- finance owners
Governance questions to answer first
| Question | Why it matters |
|---|---|
| Which teams should be isolated from each other? | Drives organization, project, and key boundaries |
| Which environments need separate keys? | Prevents staging or local usage from interfering with production |
| Who can invite members or rotate keys? | Avoids shared admin accounts and unclear ownership |
| Which model access should be available to each team? | Helps prevent accidental spend or policy violations |
| Which events need alerts or automation? | Determines email notification and webhook setup |
Recommended reading order
Availability
Enterprise capabilities can vary by customer and environment. Confirm account-specific availability before depending on SSO, webhooks, or advanced governance in production.
Implementation boundary
Enterprise pages describe governance design and customer preparation. Exact enablement steps, rollout timing, and account-specific controls can differ by customer. Do not assume a capability is active for your account until your AnyInt contact confirms it or you can see it in your account.