Perplexity Enterprise usage
Per member and per day: credits by model and by credit source, and queries. Members are stored as hashes. No thread, no prompt, no answer.
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
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Turn on the Analytics API. In the Perplexity web app, the organization's Computer settings → Analytics → Analytics API. An organization admin does this; the feature is on Enterprise plans. Open ↗
- Generate the key. In the row under the toggle, Generate key. It is org-scoped and analytics-only.
- Paste it and click Test and connect. Valistry reads the last seven complete days, reports what it found, then fills thirty.
Seats are not on this key. The directory scan finds who has Perplexity; an invoice upload prices it; both join to these rows on the same hash of the email.