Run multiple products and teams under one organization. Invite members, assign roles, scope keys to specific models or budgets, and audit every change.
Resumen de capacidades
multi
members per organization
audit-ready
permission audit log
unified
billing across products
Puntos de valor clave asignados a flujos de producción prácticos.
Beneficio
01
Role-based access
Owner, admin, and member roles control who can issue keys, change routes, and view billing.
Beneficio
02
Scoped API keys
Restrict each key to specific models, monthly token budgets, IP ranges, and request methods.
Beneficio
03
Shared billing surface
Organization-level billing rolls up usage from every API key and member into one invoice and one balance.
Un camino simple de 3 pasos para integrar esta capacidad en llamadas de pasarela, políticas de enrutamiento y controles de facturación.
Paso 1
Create organization
Set up an organization, invite members, and transfer or issue API keys under the org scope.
Paso 2
Define roles and limits
Assign roles, set per-member budgets, and scope each API key to the models it needs.
Paso 3
Review activity
Use the audit log to review key creation, role changes, and routing edits.
Yes. Each user can hold different roles across multiple organizations and switch contexts in the dashboard.
Org-scoped API keys and members are billed against the organization wallet. Personal keys bill the personal wallet.
Siguiente paso
Comience desde la documentación, el catálogo de modelos o el panel y valide esta capacidad con tráfico de producción real.