Ask what you spent with a supplier last month, and what the Spendesk wallet holds.
Connect Spendesk with a client ID and client secret and Memtro reads settlements by cleared date, type and supplier, payables, suppliers, cost centres, fees and the wallet balance. Supplier bank details are never returned. A change can take up to 24 hours to show. The hourly sync writes suppliers into memory. When asked, and once an administrator has granted the action by name, it can create, change or permanently delete cost centres, add or archive suppliers, prepare payables for accounting export, close or cancel purchase orders and offboard a user, which Spendesk cannot undo.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Spendesk tool, reads what it needs, and answers with the source cited.
These tools change something in Spendesk. 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 Spendesk 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.
Spendesk + MemtroWhat did we spend with Northwind last month?
Which card payments cleared this week, and who made them?
How much is available in the Spendesk wallet right now?
What did we pay in FX fees last quarter?
Archive the supplier Globex Print, we no longer use them
Before a renewal call the operations lead asks what the company spent with Brightwave Ltd since July. Memtro reads the settlements for that supplier, totals card and transfer payments by month, and names the cost centre each payable was booked to.
Dan Fletcher, the finance manager at Acme, asks Memtro to set up a cost centre for the Berlin office owned by Priya Nair. Memtro creates it in Spendesk with Priya as owner, and everyone in the company who picks cost centres can now choose it.
The teams that lean on Spendesk most, a question each of them asks, and what they connect beside it.
A record in Spendesk 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.
NetSuite
Ramp
FreeAgent
Holded
Mollie
QuickFile
Recurly
Airwallex
Maxio
Pennylane
Charity Commission (England and Wales)
Checkout.com
FCA Register
Soldo
Lago
Recharge
Katana
Chaser
Unleashed
Printful
Orb
Quaderno
Donorbox
Avalara AvaTax
Billy
Cin7 Core
Codat
ComplyAdvantage
inFlow Inventory
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackSpendesk's API needs a plan with API access, and an Account Owner or Admin creates the key in Settings → Integrations → Manage API access
Tick the read scopes settlement:read, payable:read, supplier:read, user:read, cost-center:read, bank-fee:read and wallet-summary:read, and for the actions only those you want, such as cost-center:manage or experimental:supplier:manage. Experimental scopes are enabled by Spendesk on request
Paste the Client ID and Client secret, shown once, into Connections → Spendesk in Memtro and connect. Fill in Company ID only for an organisation-level key across several entities
Ask what we spent with our largest supplier last month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Spendesk tools are the same everywhere.
Only when you ask, and only what it has been granted: create a cost centre with an owner and co-owners; rename a cost centre or change its owner and co-owners; delete a cost centre (permanent); add a supplier (no bank details); change a supplier's name, email or legal details (no bank details); archive or unarchive a supplier; mark a payable ready for accounting export; set a payable's accounting fields: description, accounting date, account payable, line items, amortisation; mark up to 50 settlements as manually exported; close a purchase order; cancel a purchase order; rename a user; make a user a requester or a controller; deactivate (offboard) a user from the company. 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. An hourly sync anchors recently changed Spendesk records into memory as entities.
Client ID and Client secret. Spendesk's API needs a plan with API access, and an Account Owner or Admin creates the key in Settings → Integrations → Manage API access.
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