Portkey gateway
Daily totals per virtual key: requests, errors, total tokens and the cost Portkey computed, plus the list of models it saw. Never a log, never a prompt, never a response.
Access
- Kind
- A read-only key you paste
- What to give
- Read-only API key
- Why that one
- A Portkey API key with analytics read. Valistry calls only the analytics groups, which return totals — never a log, never a prompt.
What it attributes on its own
- From the source
- day · virtual key — which usually names a team or an application · requests · errors · total tokens · what Portkey computed the day cost
- Needs a rule or a trace
- the model — Portkey's API groups cost by virtual key, and requests by model, but never the two together · input and output tokens apart · the provider's invoice · outcome
The addresses it calls
- https://api.portkey.ai/v1
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Open your Portkey API keys. Settings → API keys, as an organization owner or a workspace admin. Open ↗
- Create a key for Valistry. Analytics read is the only scope it needs.
- Paste it, name the workspace if you use more than one, click Test and connect. Valistry reads the last seven days a day at a time, reports what it found, then fills thirty.
Portkey computes a cost; the provider bills it. Connecting both Portkey and a provider behind it counts the same request twice — connect one. Portkey is the better of the two when your virtual keys already name your teams; the provider is better when you need the model or the invoice.