Credit before a launch
Tom Reilly, CTO at Acme Ltd, asked how much OpenRouter credit is left and which model cost most this week. Memtro gave credits bought, used and remaining, then spend and tokens by model for the week.
How much OpenRouter credit is left, and which model cost most this week?
OpenRouter connects Memtro to your account's usage through a management key. It reads credits bought, used and remaining, spend, requests and tokens by model, provider and day over 30 days, and the account's API keys by name with their spend and limits. It never calls a model, never shows a key value and never creates or changes a key. When asked, and once an administrator has granted them by name, it can set or remove a workspace's spend limit, and create, change or permanently delete a workspace. A limit takes effect at once and can stop a production app.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right OpenRouter tool, reads what it needs, and answers with the source cited.
These tools change something in OpenRouter. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once OpenRouter is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How much OpenRouter credit is left?
Which model cost most this week?
Which key spent most this month?
Which keys has nobody used?
Cap the staging workspace at 50 dollars a day.
Tom Reilly, CTO at Acme Ltd, asked how much OpenRouter credit is left and which model cost most this week. Memtro gave credits bought, used and remaining, then spend and tokens by model for the week.
Maya Okafor, platform engineer at BigCo, asked Memtro to cap the staging workspace at 50 dollars a day after a test loop ran overnight. Memtro read the workspace's current budgets, then set the daily limit, so OpenRouter refuses staging requests once the day's spend passes it.
The teams that lean on OpenRouter most, a question each of them asks, and what they connect beside it.
A record in OpenRouter is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In openrouter.ai, open Settings → Management keys. An ordinary key from Settings → Keys cannot read credits or activity.
Create a new key named for Memtro, with an expiry, and copy it, as it is shown once.
In Memtro, open Connections → OpenRouter (usage and credits) and paste the Management key.
Ask: how much OpenRouter credit is left?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The OpenRouter tools are the same everywhere.
Only when you ask, and only what it has been granted: set a workspace's USD spend limit for a day, week, month or lifetime; remove a workspace's spend limit for one interval; create a workspace; rename a workspace or change its slug, description or default models; delete a workspace with its budgets and guardrails. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Management key. In openrouter.ai, open Settings → Management keys. An ordinary key from Settings → Keys cannot read credits or activity.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time