OpenRouter costs, allocated and explained

What Costory does with OpenRouter

When your product routes LLM calls through OpenRouter, Costory brings the billed credits in so the agent can attribute model spend to features and teams, flag sudden increases and explain them in Slack or through Claude.

Setup in short

Create a Management API key in OpenRouter (a regular inference key cannot read analytics) and add OpenRouter from the Billing integrations in Costory. Up to a year of organization costs loads on the first sync, depending on retention.

What you can break down

Credits actually billed to your OpenRouter organization, by model or SKU when analytics fills them in, with an optional organization name as the account label. BYOK and total_usage estimates are not counted as billed spend.

Out of scope

Per serving provider or endpoint splits for now, and taxes, credits or adjustments outside the analytics API.

Full setup guide: OpenRouter in the Costory docs.