Teams

A team is a company. Everything you create belongs to the team, not to you personally. That covers collections, projects, alerts, webhooks and API keys.

You belong to one team. It is decided when you sign up. If someone invited you, you join their team. Otherwise a team is created for you, named after you until you rename it.

Inviting people

Invite colleagues from Settings → Team. They get an email and create their account from the link.

Seats are free. The team pays for API and MCP usage. Adding people does not change the bill. Their calls come out of the team's shared daily allowance, and their use of the web app is not counted at all.

Invite the people who need to see coverage. There is no reason to share one login.

Roles

Members can create and change alerts and collections. The role split is about who controls the account, not who can do the work.

API keys belong to the team

An API key acts for the team it was created in, permanently. It does not follow the person who made it.

A key stops working if its creator leaves the team, or if the team is deleted. See API intro.

Teams and projects

If you are an agency with many clients, you are one team with many projects. A project is one client. You do not need a team per client, and separate teams would mean separate bills and separate logins.

See Alerts for how projects work.

Moving between teams

You cannot currently leave or switch teams yourself. Someone who already has their own account cannot accept an invitation, because accepting would mean leaving their team.

This comes up most often when someone tried Sputnik on their own and then joins their company's team. Email peter@helpfulintelligence.co and we will move you across.

Billing

The team is the customer. One subscription, one invoice, whatever the number of people. Billing lives under Settings → Billing, and Owners and Admins can reach it.

Usage limits are per team and shared across the API, MCP and the CLI. See API intro.