What admins see
- Team spend against the monthly limit, current period.
- A summary stat row: active members, rows consumed, and API requests for the selected range.
- A team-wide rows-per-day chart.
- The per-member table with full spend columns.
What members see
The per-member usage table, searchable and sortable, defaulting to rows used. It works as a usage leaderboard: every member can see who is consuming what. Spend columns are admin-only.Time ranges and export
Pick 7, 30, or 90 days; 90 days is the bound. Both the chart and the member table export to CSV.Teams Admin API
Three read-only endpoints under/v1/team/* pull member, spend, and usage data programmatically. They require a team-scoped API key, created by an admin from the API Keys tab with the team scope selected. Personal keys receive 403 team_key_required.
GET /v1/team/members: members with roles and seat types.GET /v1/team/spend: per-member rows used and on-demand spend for the current period.GET /v1/team/usage-events: cursor-paginated usage log across the team, bounded to a 90-day look-back.
Pull the current period’s spend
Response
on_demand_spend_cents bills the team, not the member, at the flat $0.004/row overage rate.
Page through usage events
GET /v1/team/usage-events paginates with an opaque cursor and accepts limit (1 to 100, default 50) and days (1 to 90, default 30):
Response