# Attribute usage across teams and members

Turn a surface’s shared spend into per-caller and per-team accountability: know who is responsible for a call, and cap what an individual caller can spend. Field-level reference for every block here is in [Teams →](/products/affinidi-trust-fabric/agent-stream/reference/teams/teams.md) and [Members →](/products/affinidi-trust-fabric/agent-stream/reference/teams/members.md).

| Guide | What you will achieve |
| [Attribute usage to members and teams](/products/affinidi-trust-fabric/agent-stream/how-to-guides/teams/attribute-usage-to-members-and-teams.md) | Enable a surface’s team-attribution block and configure caller identity sources, so every call is attributed to a member and a team. |
| [Cap spend and rate per member](/products/affinidi-trust-fabric/agent-stream/how-to-guides/teams/cap-spend-and-rate-per-member.md) | Set a member’s monthly budget, per-minute rate caps, and model allow-list, so each caller behaves like its own virtual key. |

## Pages in this section
- [Attribute usage to members and teams](/products/affinidi-trust-fabric/agent-stream/how-to-guides/teams/attribute-usage-to-members-and-teams.md): Enable a surface's team-attribution block and configure caller identity sources, so every call is attributed to a member and a team.
- [Cap spend and rate per member](/products/affinidi-trust-fabric/agent-stream/how-to-guides/teams/cap-spend-and-rate-per-member.md): Set a member's monthly budget, per-minute rate caps, and model allow-list, so each caller behaves like its own virtual key.