Valistry

OpenRouter

Daily totals per model and upstream provider, and the key's own usage counters. No prompt, no response, no request body.

Access

Kind
A read-only key you paste
What to give
Read-only API key
Why that one
An OpenRouter API key. Valistry calls only the activity and key endpoints, both reads. Tested first, then stored encrypted; shown only as its last four characters.

What it attributes on its own

From the source
day · model · upstream provider · requests · prompt and completion tokens · what the gateway charged
Needs a rule or a trace
team, workflow and agent — a gateway key carries no caller identity unless you route one key per service · prompt caching — the activity endpoint reports no cached tokens · outcome

The addresses it calls

  • https://openrouter.ai/api/v1/auth/activity
  • https://openrouter.ai/api/v1/key

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

Connecting it

  1. Open OpenRouter's key settings. Sign in as an account owner. Open ↗
  2. Create a key for Valistry. Name it so it is recognisable in your own audit later, and leave the credit limit unset unless you want one — Valistry never spends against it.
  3. Paste it below. It is tested against the activity endpoint before it is stored.

A gateway key carries no caller identity. Routing one key per service, and naming the key after the service, is what makes a gateway attributable — the alternative is a rule in Attribution.