Valistry

Portkey gateway

Daily totals per virtual key. Each agent's share of Bedrock calls. AI calls, errors, tokens and Portkey's cost, and the models it saw. Never logs, prompts or replies.

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; the agent, by the metadata key you name: its share of each Bedrock model's calls a day
Needs a rule or a trace
the model on a virtual key's cost — Portkey's API gives a model's cost only one model at a time; input and output tokens apart; the provider's invoice; outcome

The addresses it calls

  • https://api.portkey.ai/v1

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

Connecting it

  1. Create a workspace key. Switch to the workspace Valistry should read, then API Keys → Create. Open ↗
  2. Name your Bedrock keys and agents. Open a Bedrock call in Logs. It shows the key's name and the agent's metadata. Open ↗

Connect Portkey and Amazon Bedrock together: the cost comes from Bedrock, the agents from Portkey. A day either reads is counted once. OpenAI keys in Portkey defer to OpenAI the same way.