Valistry

Perplexity Enterprise usage

Credits and questions per member and day. Each member as a code, not a name. Credits by model and by where they came from, and how many questions were asked. Never questions, answers or threads.

Access

Kind
A read-only key you paste
What to give
Analytics API key
Why that one
The organization's analytics key, which reads usage analytics and nothing else. Valistry reads credits and queries per member per day; never a thread, never a prompt.

What it attributes on its own

From the source
member (hashed); day; queries; credits, by model and by credit source
Needs a rule or a trace
the bill — Perplexity reports credits, and this key lists members with usage, not seats; tokens; team; outcome

The addresses it calls

  • https://api.perplexity.ai/v2/analytics/computer/usage
  • https://api.perplexity.ai/v1/analytics/computer/usage

Valistry calls only these addresses. It blocks any other call and logs every call.

Connecting it

  1. Turn on the Analytics API. Settings → Organization → Computer → Analytics API → Generate key. No toggle? Ask Perplexity. Open ↗

Seats are not on this key. The directory scan finds who has Perplexity, and an invoice upload prices it. Valistry matches both to this usage by the email hash.