Valistry

Claude Enterprise seats

The organization's member list: an identifier, an email, a role and the day each person joined. Never a conversation, never a prompt, never usage.

Access

Kind
A read-only key you paste
What to give
Admin API key
Why that one
An Anthropic Admin key, which reads the organization roster. Valistry calls the members endpoint only. Tested first, then stored encrypted; shown only as its last four characters.

What it attributes on its own

From the source
seat holder (hashed) · organization role · the day the seat started · seat-days in the window
Needs a rule or a trace
tokens and models per seat — the roster carries no usage · who was active — Claude Enterprise reports no per-seat activity, so an idle seat cannot be told from a busy one here · outcome

The addresses it calls

  • https://api.anthropic.com/v1/organizations/users

Only these. A call anywhere else is refused before it leaves, and every call is logged.

Connecting it

  1. Create an Admin key. Settings → Admin keys → Create. Only an organization owner can. Open ↗
  2. Find your contract seat price. The per-seat monthly figure on your Claude Enterprise order form. Claude Enterprise has no published price, so Valistry cannot look it up, and will not guess one.
  3. Paste both and click Test and connect. Valistry reads the member list, reports how many seats it found, and stores the key only if the read succeeded.

Claude Enterprise reports no per-seat activity, so Valistry cannot tell an idle seat from a busy one on this source alone. Where your people use Claude Code, the Anthropic usage connector carries the activity and the two join on the same hashed person.