Windsurf seats
Use and credits, people as codes, not names. Each member's sign-up day, role and last use. Per person, model and day: messages and credits. Never code or a 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
Valistry calls only these addresses. It blocks any other call and logs every call.
Connecting it
- Create a service key. Team settings → Service Keys. Create a new service key. Open ↗
- Find your seat price. Look on your Windsurf invoice or order form: the monthly price per seat.
The consumption endpoint allows ten requests an hour per team. If Windsurf refuses a request, seats arrive without activity, and the sync tells you.