> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.conductorquantum.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.conductorquantum.com/_mcp/server.

# Teams and team wallets

Enterprise is a plan on a Coda user. Teams are the grouping axis inside that account. There is no Coda project entity.

Each team has its own staff-loaded wallet (`team_credits`). Runs billed to a team draw from that wallet and are reported with `billed_team_id`. Creating teams is Enterprise-only.

Open **Settings → Teams** from the user menu, or go to `/chat?settings=teams`. The Overview tab shows member count, remaining team credits, and wallet spend.

![Settings → Teams overview for Conductor Quantum: 4 members, 5,000 team credits remaining, and a daily spend chart](/_fern-img/36f39e86a9ffa9b8e6b6d07769421d68255ec1bc0bd9697eaa752acae101b813.webp)

## Wallet selection

Wallet selection depends on the token and the request:

| Token                    | `team_id` on the request             | Wallet billed           |
| ------------------------ | ------------------------------------ | ----------------------- |
| Personal API token       | omitted                              | Personal wallet         |
| Personal API token       | set to a team the account belongs to | That team's wallet only |
| Team service-account key | omitted or matching                  | The key's team wallet   |
| Team service-account key | a different team                     | `400`                   |

A short team wallet returns `402` even when the personal wallet is funded. The request never falls back to the personal wallet. Load each team wallet (by Conductor staff) before billing runs to it.

```python
from conductorquantum import ConductorQuantum

client = ConductorQuantum(token="<your-api-key>")
for event in client.coda.agents.run(
    messages=[{"role": "user", "content": "Explain a Bell state in one sentence."}],
    team_id="<team-id>",
):
    print(event)
```

`POST /qpus` accepts the same optional `team_id` field.

## Members

Owners invite members by email. The roster shows role and charged credits for the selected window.

![Settings → Teams members tab showing Sofia Reyes as owner with Priya Nair, Marcus Webb, and Elena Voss](/_fern-img/d618f879787ed626dd57b182fd60fb265a253ea8cc2f135657b4a93d2243dc44.webp)

The same roster is available from the API. These endpoints use the same bearer token (`mcp:read` or `agents:run`) and are not available on `/mcp`.

| Endpoint                       | Purpose                            |
| ------------------------------ | ---------------------------------- |
| `GET /teams`                   | Teams the token account belongs to |
| `GET /teams/{team_id}`         | Team metadata and member roster    |
| `GET /teams/{team_id}/members` | Member `user_id`, email, and role  |

A team service-account token returns only its own team.

```python
teams = client.coda.teams.list()
detail = client.coda.teams.get("<team-id>")
members = client.coda.teams.members.list("<team-id>")
```

`GET /teams/{team_id}` returns each member's `user_id`, email, role, and `joined_at`. Owners and team service-account tokens also receive that member's requested/charged credits and tokens for the query window (`since` / `until`). Non-owner members see the roster without other people's spend.

## Usage

The Usage tab lists attributed queries for the team wallet. Export CSV from the same view.

![Settings → Teams usage tab with per-run attributed queries and CSV export](/_fern-img/c62b1c340a69025347455ed44c74ae14586d691a54f801447f414b35a20c64ce.webp)

Attributed usage is also available at `GET /usage/teams/{team_id}`. Charge fields and the pull API are on [Usage and credits](/coda/usage/usage-and-credits). Organisation-level remaining credits and the credit ledger stay under **Settings → Billing**.

## Keys

Enterprise owners mint personal tokens and team service-account keys here. Secrets are shown once.

![Settings → Teams keys tab for minting a team service-account key and enabling a usage callback URL](/_fern-img/cc582233c6d0855d13ba5654c5245c6f81800099250fad7d2656b0ee40af25c5.webp)

> **Warning**
>
> API keys cannot be created through the Coda API.

The same tab configures a signed usage webhook. See [Usage callbacks](/coda/usage/usage-callbacks).

See the [Coda API Reference](/api-reference/coda-api) for full schemas.