Weekly spend check
Dan Fletcher, ML lead at BigCo, asked what Runpod cost last week. Memtro split spend in USD by day and by pod, and named the running pods with their hourly cost.
Which GPU pods are running, and what are they costing us?
Runpod shows you your pods with GPU, image, status, hourly cost and live utilisation. It reads serverless endpoints with their workers and request metrics, network volumes, GPU types with prices, and spend by day, pod or endpoint. When asked and granted, it can create, start, stop, restart, change or terminate a pod. It can also rescale or delete a serverless endpoint, and create, grow or delete a network volume. Creating or starting a pod starts hourly billing. Memtro never reads environment variables, secrets, SSH keys or registry credentials.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Runpod tool, reads what it needs, and answers with the source cited.
These tools change something in Runpod. 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 Runpod 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.
Which pods are running and what do they cost per hour?
What did we spend on Runpod last month?
How busy is the GPU on the training pod?
How many requests failed on the inference endpoint today?
What does an H100 cost per hour on secure cloud?
Dan Fletcher, ML lead at BigCo, asked what Runpod cost last week. Memtro split spend in USD by day and by pod, and named the running pods with their hourly cost.
Maya Okafor at Acme Ltd saw an idle training pod and asked Memtro to stop it. With the action granted, Memtro stopped it, so compute billing ended while its disk was kept.
The teams that lean on Runpod most, a question each of them asks, and what they connect beside it.
A record in Runpod 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 the Runpod console open Settings, then API Keys, and create a key. Choose Read Only for reads, or All for actions. It is shown once.
In Memtro open Connections → Runpod and paste the API key.
A key made inside a team acts for that team. An administrator grants the pod, endpoint and volume actions by name.
Ask: which pods are running and what do they cost per hour?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Runpod tools are the same everywhere.
Only when you ask, and only what it has been granted: create a pod (starts hourly GPU or CPU billing); start a stopped pod (resumes billing); stop a running pod (keeps its disk); restart a running pod's container; terminate a pod (permanent); rename a pod, change its image, disk, ports or lock; rescale or change a serverless endpoint; delete a serverless endpoint (permanent); create a network volume (billed storage); rename or grow a network volume; delete a network volume (permanent). 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.
API key. In the Runpod console open Settings, then API Keys, and create a key. Choose Read Only for reads, or All for actions. It is shown once.
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