Team
Invite teammates to your SerpKite account so they can manage keys, watch usage and buy credits on one shared balance, while the owner keeps control of settings and the account.
How teams work
A SerpKite account belongs to one owner. The owner can invite other people as members. Members sign in with their own email, GitHub or Google login, and then act on the owner’s account: the same balance, the same API keys, the same usage and billing history.
- A user either owns an account or is a member of exactly one other account.
- The number of seats (members including the owner) is shown on the Team page. The default is 2 seats (the owner and one teammate); contact us if you need more.
- Credits are shared. There is no per-member balance; use per-key limits and the member key limit if you need budgets per person or service.
Roles
| Action | Owner | Member |
|---|---|---|
| Use the account’s balance and rate limit | Yes | Yes |
| View usage, request log and CSV export | Yes | Yes |
| Create API keys; rename, rotate and revoke the ones you created | Yes | Yes |
| Set key limits and the member key limit; manage keys other people created | Yes | No |
| Buy credit packs, view orders and invoices | Yes | Yes |
| Invite and remove members, cancel invites | Yes | No |
| Change spend controls, alerts and webhook settings | Yes | No |
| Rotate the webhook signing secret | Yes | No |
| Delete the account | Yes | No |
| Leave the team | n/a | Yes |
Each API key records who created it, so the key list shows which teammate made which key.
Member key limit
The owner can set a default monthly credit limit for keys that members create on the Team page. Every key a member creates from then on gets that limit, and only the owner can change it afterwards. Members can rename, rotate and revoke their own keys, but can’t raise, lower or remove a key’s limit, and rotating a key keeps its limit.
- By default there is no member key limit, so keys members create have no limit until the owner sets one.
- Changing or clearing it applies only to keys created afterwards. Existing keys keep their limit; the owner edits those one by one on the API keys page.
- Keys the owner creates don’t get the member key limit; the owner picks each key’s limit.
- Members can see the current member key limit on the Team page.
Invite someone
-
Send the invite
The owner opens Team in the dashboard, enters the teammate’s email and clicks Invite. An email with an accept link goes out. Pending invites are listed with their expiry date and can be cancelled.
-
Accept it
The teammate opens the link and signs in (or signs up) with the invited email address. The invite can only be accepted by a user with that email.
-
Start working
After accepting, the dashboard shows the owner’s account. Balance, keys and usage are the team’s.
A user can act on only one account. If the invited person already uses SerpKite on their own account, they should use up or move that work first; contact support if you need to merge accounts.
Remove a member or leave
- The owner can remove any member from the Team page. The member’s own login keeps working, but they lose access to the account’s keys, usage and billing.
- A member can leave the team from the same page.
API keys belong to the account, not to the person who created them. Removing a member does not revoke the keys they created. If they had access to secrets, rotate those keys.
Deleting the account
Only the owner can delete the account. Deleting it permanently removes the account, its keys and its remaining credits, and members lose access. Deletion requires typing the owner’s email to confirm.
Related
Last updated: 2026-09-29