Personal billing
The key spends against the individual account. This is useful when a user is experimenting independently or needs separate cost ownership.
Team Management
Teams let organizations centralize credits, group authorization, and member access. This page explains the operational model so teams know what becomes shared and what stays per-user.
What Teams Change
Teams introduce shared billing and shared operational control, not just shared visibility.
A team can centralize credits, invite members, manage shared groups, and let owners review usage from one place.
That means team setup is not just an access convenience. It changes who pays, which groups members can use, and how member activity is governed.
Shared billing means credits can come from the team rather than from each member separately.
Shared groups let the team define which model paths are available to team-issued keys.
Member-level limits still matter even when the team pays centrally.
Create or Apply for a Team
The UI supports team onboarding as an application flow, followed by an active team dashboard after approval.
01
Submit the team application
Provide the team name, expected member count, and the usage context that helps the review process.
02
Wait for review status
A team may stay pending until review is complete. After approval, the team dashboard becomes the main workspace for owners.
03
Set the initial shared groups
Define the group access the team wants to expose before inviting many members.
Personal Billing vs Shared Billing
The distinction matters when teams decide whether a key should spend from the user account or from the team account.
Shared billing
The key spends against the team account and uses the team-managed group authorization model.
Why this matters
A team key can inherit the team's operational guardrails, while a personal key can remain intentionally separate.
Invite Members and Control Spend
Member management combines invitation, usage oversight, and optional spend controls.
01
Invite the member
Owners can invite members by email from the team dashboard.
02
Set a member limit when needed
Use member-level limits when the team wants a clear budget boundary for a particular user or function.
03
Review team usage regularly
Team usage panels help owners understand where credits are going before cost surprises accumulate.
Team Dashboard Screenshots
Reserve space for the team dashboard, member management, and team usage views.
Team overview cards
Shows the team dashboard summary cards and member management context.
Member invitation dialog
Shows the invitation flow for adding a team member and setting an optional limit.
Groups tab
Shows the team's model group bindings and group authorization state.
Team usage panel
Shows team-level usage and spending context for owners.
These views show the team owner workflows for overview, invitations, group access, and usage review.