One account, everyone's agent
The first thing a customer did after their agent made a good video was ask how the rest of the team could make one. Not by sharing an API key around. By letting the CEO's agent, the ops lead's agent and the account executive's agent all work from the same brand kit, the same stored characters and the same finished footage, each under their own name.
That's live.
Members, roles, keys
An admin adds a person — name, role, optional monthly credit cap — and gets back that person's own
API key, once. The person puts it in whatever they use: Claude, a custom agent, the local MCP
server. From then on whoami says who they are, and every job, asset, brand kit, character, post
and bug report they create carries their name.
Three roles. Admin does everything, including members, keys, approvals and the provider keys. Creator makes things and drafts posts. Reviewer reads everything, approves or rejects posts, and files reports — and cannot spend a credit. Change a role and the person's keys change with it; remove someone and their keys stop at once, while what they made stays with the team.
The library
Everything on an account was already shared by construction. Now there's one call that shows it:
library lists the brand kits, stored characters (with their sheets), analyzed styles, finished
videos and uploads, each with who made it. An agent asked to "put Urav in the brand's colors" finds
both by id before it creates anything.
Spend you can see
Credits are attributed per person on every ledger line, so the members list is also the bill.
A cap stops a job before it runs — 402 member_cap, with the cap, what's spent and what the job
would cost — and refunds for failed jobs go back to the same person.
Read the Team docs. If you're already on an account, your admin can invite you today.