Before the offsite
The office manager asks whether the Events wallet can cover a team offsite. Memtro reads the wallet and answers that £3,200 is available and £400 blocked, and lists two pending spending requests from Priya Nair for travel.
Ask how much is left in a team's Soldo wallet, and which expense reports await processing.
Connect Soldo with a client ID and secret and Memtro reads wallets, cards with the last four digits only, people, groups, expense reports and spending requests. Card numbers, bank details and dates of birth are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can approve a spending request, which releases company money and cannot be undone here, or decline one, review expenses, process expense reports, tag and categorise transactions, and create groups and categories.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Soldo tool, reads what it needs, and answers with the source cited.
These tools change something in Soldo. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Soldo, choosing the same kinds; the tab shows Soldo's own steps. Each event can start a job, with the event as its input. Soldo signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Soldo 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 is left in the Marketing team's wallet?
Which cards are marked lost or expired?
Which expense reports are still to be processed, and how much is to reimburse?
What spending requests are pending approval?
Approve Priya Nair's £400 travel request from the Events wallet
The office manager asks whether the Events wallet can cover a team offsite. Memtro reads the wallet and answers that £3,200 is available and £400 blocked, and lists two pending spending requests from Priya Nair for travel.
Laura Bennett, finance lead at Northwind, asks Memtro to approve Priya Nair's £400 train fares request. Memtro reads it back with the amount, then approves it from the Events wallet, which releases the money to Priya's card, and Soldo may notify her.
The teams that lean on Soldo most, a question each of them asks, and what they connect beside it.
A record in Soldo 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 Soldo web app open Integrations → Business API → Create application, paste the public key of a 2048-bit RSA pair and tick the View scopes for Company, Wallets, Cards, Users, Groups, Expense report, Requests, Expense review, Expense categories and Tags
Tick Edit scopes only for what Memtro may act on: Requests, Expense review, Expense report, Transactions, Groups, Tags or Expense categories. Then complete strong customer authentication
Copy the Client ID and Client secret from the popup into Connections → Soldo in Memtro and connect. Memtro never asks for the private key or Fingerprint token, so keep those to yourself
Ask how much is left in the Marketing wallet
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Soldo tools are the same everywhere.
Only when you ask, and only what it has been granted: approve a spending request for funds or goods and services (releases company money); decline a spending request with a note; approve, partially approve, deny or reopen an expense review; ask a person for more information on an expense; remind a person to submit their expenses for a period; mark an expense report processed, or cancel it; add a list tag to a transaction; set a transaction's expense category (replaces the one there); create a group; update a group's name, reference, note or type; add a tag to an expense list; create an expense category. 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.
Client ID and Client secret. In the Soldo web app open Integrations → Business API → Create application, paste the public key of a 2048-bit RSA pair and tick the View scopes for Company, Wallets, Cards, Users, Groups, Expense report, Requests, Expense review, Expense categories and Tags.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Soldo, choosing the same kinds; the tab shows Soldo's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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