Teams & roles

One company, one balance, one invoice. Everyone gets their own login and their own API key, and every key spends from the same pot. Seats are free: you pay for tokens, not per person.

Balance: Shared by the whole team
Keys: One per person, owned by the company
Invoice: One, not one per developer
Seats: Free, unlimited

Your two accounts

Everybody has a personal account from the day they sign up. Joining a company adds a team account next to it. You do not pick one forever: the switcher at the top of the console says which one you are in right now.

In the switcher	Whose money you spend	Which keys you see
Acme (team)	Acme’s shared balance	Every key the team owns
Your name (personal)	Your own balance	Only your own keys

A key belongs to an account, not to a person.Make a key while you are in Acme and it is Acme’s key, spending Acme’s credits, and it keeps working after you leave. If the team is the only one you belong to, signing in puts you straight into it, on any browser or device.

The five roles

Role	Keys	See balance	Pay & withdraw	Manage people	Best for
Owner	Yes	Yes	Yes	Yes	You, the person who pays
Admin	Yes	Yes	No	Yes	Eng lead who should see spend
Developer	Yes	No	No	View only	Engineers shipping code
Billing	No	Yes	Yes	View only	Finance, no code access
Viewer	View only	Yes	No	View only	Stakeholder who just watches

Everyone, in every role, can see usage and activity.

Two things that surprise people. A Developer cannot see the balance, so if your engineers should watch the spend, make them an Admin. And key access is not per person: anyone who can manage keys can revoke anyone’s key, not just their own. Use Viewer for someone who should look but not touch.

Only an owner can invite or remove another owner, hand over ownership, or delete the organization.

Adding your team

Open Settings and invite the person by email, picking their role.
They get a link, sign in with that same address, and confirm their email.
They land in your company with their role, and a key of their own already made.

That key is the company’s, so their very first request spends the shared balance. No card, no personal top-up, nothing to wire up. Invites work once, expire after 7 days, and can be revoked or resent at any time; up to 50 can be pending at once.

Paying for it

Credits sit on the company. Anyone with key access spends them, no personal card needed.
Only Owner and Billing can top up, redeem a code, or withdraw cashback.
Teams start on the Scale rate plan, so you are not sharing one person’s signup limits.

A new company starts at $0. Add credit before handing out keys, or the first request returns 402 and your developer sees an insufficient-credit error on a key that is perfectly valid. Credit cannot be moved from a personal balance into a company yet, so top the company up directly.

People leaving, and shutting down

Remove someone and they lose access immediately. Every key stays with the company, including the ones they made, because the keys were never theirs.
The last owner cannot leave. Hand ownership to someone else first, or delete the organization.
Deleting is blocked while any credit or cashback is left: spend, redeem or withdraw first. Deleting then revokes every key and keeps your invoices and history.

Past usage never moves. Requests stay attributed to whoever served them, so last month’s report still reads the same next year.

Which setup do you want?

You are	Use
One developer on your own projects	Your personal account. Nothing to set up.
A company with a few developers	One organization. Developer for engineers, Admin or Billing for whoever owns the spend.
Reselling inference to your own customers	Child keys, not members. One key per customer, with its own budget.

Need SSO, finer key permissions, or something not covered here? Email support@straitly.ai.