Usage before a renewal
Dan Fletcher, account manager at Acme Ltd, asked how many API calls BigCo had used this month. Memtro read the usage on BigCo's active subscription and gave the total for the billing period with the daily series beside it.
How much has this customer used, and what have we billed them?
Orb connects Memtro to your usage-based billing. It reads customers with balance and currency, subscriptions with plan, status and billing period, metered usage per billable metric as a total and a daily series, invoices by status and date, and plans with their prices. When asked, and once an administrator has granted the action by name, it can create and edit customers, start, change or cancel subscriptions, which bills or may invoice the customer, issue invoices that may email and charge them, void an invoice permanently, adjust prepaid credits and issue credit notes that give money back.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Orb tool, reads what it needs, and answers with the source cited.
These tools change something in Orb. 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 Orb, choosing the same kinds; the tab shows Orb's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Orb signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Orb 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 usage has Acme had this billing period?
Which invoices are still unpaid?
Which subscriptions have a trial ending this month?
What is the current balance on Northwind's account?
Cancel Globex's subscription at the end of its term
Dan Fletcher, account manager at Acme Ltd, asked how many API calls BigCo had used this month. Memtro read the usage on BigCo's active subscription and gave the total for the billing period with the daily series beside it.
Sarah Chen, finance manager at Northwind, asked Memtro to cancel Globex's subscription at the end of its term. Memtro scheduled the cancellation in Orb, so Globex is billed to the end of the term and the subscription does not renew. Nobody at Globex was invoiced early.
The teams that lean on Orb most, a question each of them asks, and what they connect beside it.
A record in Orb 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 Orb app, open Developers → API keys.
Create a key in live mode, with read access to customers, subscriptions, invoices and plans, and write access only to the areas you want Memtro to act on.
In Memtro, open Connections → Orb and paste it into API key.
Ask your first question: how much usage has Acme had this billing period?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Orb tools are the same everywhere.
Only when you ask, and only what it has been granted: create a billing customer; edit a customer's name, email, currency, invoicing flags or metadata; start a subscription to a plan for a customer (starts billing them); cancel a subscription now, at term end or on a date (may invoice the customer); withdraw a scheduled subscription cancellation; change a subscription's plan now, at term end or on a date (may invoice the customer); withdraw all scheduled plan changes on a subscription; edit a subscription's memo, net terms, collection and issuance flags, threshold or metadata; move a subscription's trial end date, or end the trial now; create a one-off invoice, as a draft unless auto-issue is asked for; edit an invoice's dates, net terms, auto-collection or metadata; issue a draft invoice (may email the customer and collect payment); void an issued invoice (permanent); mark an issued invoice as paid; add, deduct or re-date a customer's prepaid credits; issue a credit note against an invoice's line items (gives money back to the customer). 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 Orb app, open Developers → API keys.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Orb, choosing the same kinds; the tab shows Orb'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