Windsurf seats
The roster with sign-up time, role and last feature use, and per member, per model and per day: messages and credits or ACUs. People are stored as hashes. No code, no prompt.
Access
- Kind
- A read-only key you paste
- What to give
- Service key
- Why that one
- A Windsurf service key with Analytics Read. Valistry reads the team roster and each member's daily consumption; never code, never a prompt.
What it attributes on its own
- From the source
- seat holder (hashed) · seat-days from sign-up · model, messages and credits per member per day · last use of autocomplete, chat and command
- Needs a rule or a trace
- the bill — Windsurf reports credits, so seats are priced at the figure you enter · tokens per message · team or project · outcome
The addresses it calls
- https://server.codeium.com/api/v1/UserPageAnalytics
- https://server.codeium.com/api/v2alpha/analytics/consumption
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Create a service key. Team settings → Service keys → Add service key. Analytics Read is enough; Teams Read-only is the least the roster needs. Open ↗
- Find your seat price. The per-seat monthly figure on your invoice.
- Paste both and click Test and connect. Valistry reads the roster and seven days of consumption, reports what it found, then fills thirty.
The consumption endpoint allows ten requests an hour per team. Valistry makes one page-walk per run, and when it is refused the seats land without activity and the run says so.