How much was Acme invoiced last quarter, and what credit is left?
Metronome connects Memtro to your usage-based billing. It reads customers, their contracts with commits and credits, invoices with totals and line items, and commit and credit balances. It also reads metered usage by day or hour, customer alerts and products. When asked and granted, it can create, rename or archive customers, set custom fields, create, end or archive contracts, grant credits, adjust balances, void or regenerate invoices, manage alerts and send usage events. Metronome can also tell Memtro as balances cross thresholds or invoices finalise, and a job can start on it. Amounts are often in USD cents.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Metronome tool, reads what it needs, and answers with the source cited.
These tools change something in Metronome. 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 Metronome, choosing the same kinds; the tab shows Metronome's own steps. Each event can start a job, with the event as its input. Metronome signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Metronome 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.
Metronome + MemtroHow much was Acme invoiced last quarter?
What is left on BigCo's prepaid commit?
How much API usage did Northwind record yesterday, by hour?
Which customer alerts are in alarm right now?
Grant Northwind a 500 dollar credit on the platform product for this month.
Priya Sharma, finance manager at Acme Ltd, asked how much BigCo was invoiced last quarter. Memtro read BigCo's invoices with their totals and line items. She had the answer for the account review without exporting a report.
When Northwind's credit balance fell below its threshold, Metronome told Memtro and a job started. It read Northwind's balances and recent usage and summarised them for Dan Fletcher, the account manager. No credit was granted until he asked.
The teams that lean on Metronome most, a question each of them asks, and what they connect beside it.
A record in Metronome 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
Spendesk
Lago
Recharge
Katana
Chaser
Unleashed
Printful
Orb
Quaderno
Donorbox
Avalara AvaTax
Billy
Cin7 Core
Codat
ComplyAdvantage
inFlow Inventory
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn the Metronome app, open Developer → API tokens and add a token named Memtro. It has the permissions of its creator and is shown once. A sandbox token is good for trying actions first.
In Memtro, open Connections → Metronome and paste the API token.
An administrator grants the actions by name, such as Void an invoice, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added under Developer → Notifications → Webhooks.
Ask "How much was Acme invoiced last quarter?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Metronome tools are the same everywhere.
Only when you ask, and only what it has been granted: create a customer; rename a customer; archive a customer and its contracts; set custom field values on a customer, contract, invoice or other record; create a contract for a customer from a rate card or package; change or remove a contract's end date; archive a contract, optionally voiding its invoices; grant a customer a credit; add a manual entry to a commit or credit balance; void an invoice; regenerate a voided invoice; create a threshold alert for a customer; archive an alert; send usage events for billing. 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 token. In the Metronome app, open Developer → API tokens and add a token named Memtro. It has the permissions of its creator and is shown once. A sandbox token is good for trying actions first.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Metronome, choosing the same kinds; the tab shows Metronome'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