Skip to main content
Everything belongs to your organization: API keys, credits, usage, and billing. Whoever signs up creates it and becomes its first org admin; everyone else joins by invitation from the Organization page and gets a role that scopes what they can do.

What each role can do

In practice, the roles map to jobs:
  • Org admin, full control, including the only role that can manage members and grant org-admin. Keep at least two, so no one person is a single point of failure.
  • Billing admin, finance without engineering access: credits, auto-recharge, payment history, invoices, and inviting teammates.
  • Developer, day-to-day API work: keys and the playground, but no spending controls.
  • Viewer, read-only visibility (usage, models, existing key names) for stakeholders who ship nothing.

Inviting teammates

Enter an email and pick a role, the invitee gets an email, and the pending invitation (with a copyable invite link) stays listed until it’s accepted or revoked. Accepting routes through sign-in and lands the new member inside your organization, they never create a duplicate org of their own. Roles can be changed (and members removed) by an org admin at any time; changes take effect on the member’s next session refresh.
Stripe receipts and invoices go to your organization’s billing contact: the earliest-joined billing admin, falling back to the earliest org admin. Changing those roles re-points it automatically.