Developers / Organizations
Organizations
Manage shared access while preserving personal account boundaries.
Organizations
An organization owns its API keys, credits, usage, activity and audit history independently of its members. Create one in Settings, with a recent passkey confirmation. Invite people explicitly; roles and current membership are checked by the platform on each request.
Account Boundaries
Personal keys act for their personal account. Organization keys act only for their organization. Removing a member or suspending the organization revokes access without granting access to personal work.
Integrating An Application
Select the intended tenant before creating a key. Its capabilities and usage belong to that tenant; a team key is not a route into a member's personal Workspace. Current membership and role checks still apply to interactive operations. Keep the key on a trusted server and retain request IDs when reconciling usage.
Owner-session organization controls are separate from the published API-key contracts. Read Platform Integration for host, principal and lifecycle boundaries.