OpenRouter
What Plutus imports
Section titled “What Plutus imports”- Credit spend by model
- Credit spend by API key (per-key chargeback)
- BYOK inference spend, tracked separately so it is never double-counted
Connecting
Section titled “Connecting”Method: Management API Key
- In OpenRouter, go to
openrouter.ai/settings/management-keysand create a management key. This is not the same thing as an inference key (the kind you use to call models, created atopenrouter.ai/keys) — a key from that page gets a 403 when Plutus tries to use it. - Copy the management key. OpenRouter only shows it once. Both management and inference keys
start with
sk-or-v1-, so they look identical once copied — if the sync fails with a 403, you most likely pasted an inference key by mistake. - In Plutus, paste the key into the Management API Key field and save.
- In OpenRouter, name your inference keys after the team, service, or person that uses them. Plutus reports spend per key for chargeback, and OpenRouter’s Analytics API returns each key’s name rather than its ID — so whatever you name a key there is what shows up in Plutus’s breakdown.
Cost is what OpenRouter charges your credit balance. Inference you pay an upstream provider for directly (BYOK) is deliberately excluded from the totals — you are already billed for it on that provider’s own account, and counting it here too would double it — but it is still tracked, as its own “BYOK inference” line under Usage Type.