Account

Projects and teams

Split one account's keys, spend and logs into projects, one per client, product or environment, and bring in teammates who share the balance and plan.

Projects#

Every account starts with a Default project; create more under Developers → API projects (up to 100). Each API key belongs to one project, and the project picker at the top of the dashboard scopes API keys, Usage and Logs to it. The web chat spends in the default project. Request and response body logging is switched on per project; see Data privacy.

Projects don't change the API: a key's project is known from the key, so nothing extra is sent with requests.

Project budgets#

A monthly budget is a hard cap across all of a project's keys. Once the project has spent it in the calendar month (UTC), its calls are refused with 429 project_budget_reached until the month turns or you raise the budget. Other projects keep working. Keys can also carry their own caps inside a project; see Rate limits and quotas.

Who can use a project#

A project is open to the whole team, or only to the members you pick. Owners and admins always see every project. Members see the projects open to them, and the keys and logs within them.

Archiving#

Archiving a project revokes its keys at once (their calls get 401 project_archived); its usage and logs stay. The default project can't be archived.

Teams and roles#

Invite people by email under Team. Everyone on a team spends the team's prepaid balance and plan allowance, and every request is logged with the key that made it.

Role	Can do
Owner	Everything, including closing the account. The account's creator.
Admin	Billing and plans, inviting and removing people, every project and every key.
Member	Create and manage their own keys, use the chat, and see the projects open to them.

Removing someone revokes every key they created on the team. Changes to people, keys, budgets and billing are recorded in the dashboard's Activity log.

Stuck? Email [email protected]System status Changelog