Setup
Teams
Each teammate holds their own key, usage settles on the team account, and revocation is per key.
A team is an organisation whose keys bill the owner’s account. There is no button in the console to create one yet, so write to us and we will set it up. Your admin then sends you an invite code. Paste it into the team panel in the console and mint a company key on /console#/keys, or use one your admin minted for you. Save it as CONIFER_API_KEY and everything on The API key applies unchanged. You do not need a personal card.
What a team key can do
| Models | The whole catalog, unless your admin scoped the key to a list of models. Scope follows the live catalog, so a new model needs no re-mint. |
| Billing | Every request settles on the owner's account at the catalog prices. Each response carries its cost receipt. |
| Roles | Owner, admin and member. Owners and admins mint keys and see team usage. A member holds one live company key at a time. |
| Invites | Invite codes last 7 days. |
| Revocation | Per key, in effect within seconds. Other keys are not affected. Leaving or being removed revokes your company keys. |
Across machines
A team key carries the model scope and the spend cap. Which model a request names, or whether Conifer chooses, is up to each caller. See Routing. Keeping a particular machine on its own hardware is set per machine in the CLI and is covered under Run a model.