Share one balance with your team

23 September 20263 min read

MiniRouter and Teams, separated by a silver fold of light on black.

A team is one prepaid balance up to 10 people share. Every member keeps their own keys and logs. Create one from Team in the dashboard; it costs nothing and your personal account stays yours.

One balanceThe owner tops it up. Every team key bills it.
Your own keysMade in the team, attributed to you.
Your own logsMembers see their own usage and activity.

Every team key bills the team

A key made inside a team looks like any other MiniRouter key. Requests draw from the team balance and are logged under the member who made the key.

Team key request · cURL

curl --include https://api.minirouter.sh/v1/chat/completions \
  -H "Authorization: Bearer $TEAM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "zai/glm-5.3-flash",
    "messages": [{ "role": "user", "content": "One line: what is a team?" }],
    "max_tokens": 64
  }'

Response headers

HTTP/2 200
x-minirouter-balance-usd: 248.10
x-minirouter-cost-usd: 0.000031

is the team balance after this request, on every response, for every member. Only the owner tops up; low-balance alerts go to the owner.

Switch in one tap

Personal or team, from the pill in the rail. Every page shows the account you are in.

PersonalAcme · Owner

Invite by link

One link per team, valid 7 days, shown once. People sign in and press Join. Regenerate it any time; the old link stops working.

minirouter.sh/join/8f2…c1JLSRAP3 of 10

Owner and members

OwnerFunds the team, sets limits, routing and alerts, invites and removes.
MemberMakes keys, presets and guardrails. Sees their own logs and the balance.

Create, name, rotate and revoke own keys: Owner and members
Set key limits and guardrails: Owner
See keys, usage and activity: Members see their own. The owner sees everyone's.
Create presets and guardrails: Owner and members
Top up, billing history and export: Owner
Routing and alerts: Owner

Members create presets and guardrails; the creator or the owner edits them. Key spend limits and per-key guardrails are the owner's.

Removing someone

The owner picks what happens to a removed member's keys.

Revoke nowTheir next request is refused. A stream already running finishes.
Keep keys activeThe ex-member still holds them, and they keep billing the team.

Leaving revokes your keys. Removal and leaving both end the member's team sessions and replace the invite link.

Limits

Members per team: 10
Teams you can own: 3
To create one: $0

Account limits apply to the team as a whole. Settings, sign-in methods, provider keys and plans stay on your personal account; see personal account only.

Create a team Read the docs