Checking cloud spend
Maya Okafor, finance manager at Acme Ltd, asked what the Public Cloud project had cost so far this month. Memtro read the usage and gave the total with the cost per resource type and when it was last updated.
What is our OVHcloud bill so far this month, and is every server running?
OVHcloud hosts your servers and domains, and Memtro reads the account for you. It reads bills with amounts, and Public Cloud projects with their instances and current-month usage cost. It also reads VPS, dedicated servers with datacenter, power state and OS, and DNS zones with their records. When asked and granted, it can reboot, start or stop a cloud instance or a VPS, and reboot a dedicated server. It can also create, change or delete DNS records and publish a zone's changes. Keys only work in the region that issued them.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right OVHcloud tool, reads what it needs, and answers with the source cited.
These tools change something in OVHcloud. 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 OVHcloud 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.
What has this month's Public Cloud usage cost so far?
Which instances are shut off or in error?
What were our last three OVHcloud bills?
What records are in the acme.co.uk DNS zone?
Reboot the staging VPS.
Maya Okafor, finance manager at Acme Ltd, asked what the Public Cloud project had cost so far this month. Memtro read the usage and gave the total with the cost per resource type and when it was last updated.
Tom Reilly, platform engineer at Northwind, asked Memtro to point the shop subdomain at the new server. Memtro changed the record's target and published the zone, so the change went live on OVHcloud's name servers.
The teams that lean on OVHcloud most, a question each of them asks, and what they connect beside it.
A record in OVHcloud 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.
On the createToken page for your region, log in, name the application and add only the rights Memtro may use. GET rights are enough for reading. Copy the three keys, as the secret is shown once.
In Memtro, open Connections → OVHcloud and enter the Region (eu, ca or us), then the Application key, Application secret and Consumer key.
Add POST, PUT or DELETE rights only for the restarts and DNS changes you allow. An administrator then grants those actions by name to the engineers who may use them.
Ask what this month's Public Cloud usage has cost so far.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The OVHcloud tools are the same everywhere.
Only when you ask, and only what it has been granted: reboot a Public Cloud instance (soft or hard); start a stopped Public Cloud instance; stop a Public Cloud instance; reboot a VPS; start a VPS; stop a VPS; reboot a dedicated server; create a DNS record; change a DNS record's target, subdomain or TTL; delete a DNS record; publish a DNS zone's pending changes. 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.
Region, Application key, Application secret and Consumer key. On the createToken page for your region, log in, name the application and add only the rights Memtro may use. GET rights are enough for reading. Copy the three keys, as the secret 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