MRR, churn, customers and every upgrade or cancellation, straight from Baremetrics.
Connect Baremetrics with the account's API key and Memtro reads MRR, ARR, net revenue, ARPU, LTV, active customers and churn for any period, one metric as a daily series or per plan, customers with their plans and event history, the event stream of upgrades, downgrades and cancellations, and chart annotations. There is no sync: each answer is read live. When you ask, and once an administrator has granted the action by name, it can add or delete annotations and goals, and record customers, plans, subscriptions, cancellations, charges and refunds. These record figures that change your reports, and no money moves.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Baremetrics tool, reads what it needs, and answers with the source cited.
These tools change something in Baremetrics. 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 Baremetrics 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 was MRR at the end of October, and how does it compare with 30 days earlier?
Who cancelled in the last 7 days, and what plan were they on?
Which customers have the highest lifetime value?
What has happened on Acme Ltd's account since they signed up?
Add an annotation on 1 November to every chart saying the new pricing went live
The CEO asks on Friday what MRR did this month and whether churn is up. Memtro reads the period's summary from Baremetrics, gives MRR, net revenue and user churn on the first and last day, and lists the cancellations behind the change.
Olivia Hart, head of finance at Globex, asks Memtro to set a goal of 120,000 MRR by the end of March and mark today's price change on the charts. Memtro creates the goal and the annotation, credited to Olivia, and both show to everyone with access to the account.
The teams that lean on Baremetrics most, a question each of them asks, and what they connect beside it.
A record in Baremetrics 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.
CallRail
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowIn Baremetrics open Settings → API and copy the account's API key. It reads everything, and also makes the changes an administrator grants
In Memtro open Connections → Baremetrics, paste the API key and connect. Memtro reads the account and its sources (Stripe, Braintree, Chargebee, Recurly or the Baremetrics API) and uses the first source by default
Amounts come back in whole units of the account's currency rather than cents, and rate metrics such as user churn come back as Baremetrics sends them, in hundredths of a percent (590 for 5.90%)
Ask what MRR did over the last 30 days, or who cancelled this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Baremetrics tools are the same everywhere.
Only when you ask, and only what it has been granted: add an annotation to the charts (a launch, a price change); delete a chart annotation (permanent); set a goal for a metric over a date range; delete a goal (permanent); add a customer to a source; change a customer's name, email or notes; add a plan to a source; record a subscription, which changes MRR; record a subscription's cancellation, which counts as churn; record a one-off charge (no money moves); record a refund against a recorded charge (no money moves). 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 Baremetrics open Settings → API and copy the account's API key. It reads everything, and also makes the changes an administrator grants.
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
