Commerce & Payments · Integration
Baremetrics
Add Baremetrics to your product for your customers, and give your AI agents governed access to it.
Baremetrics sits on top of a payment processor rather than holding the billing data itself, so almost every path is scoped by a source id: /v1/{sourceId}/customers, /subscriptions, /plans and /charges. The first call you make should be GET /v1/account, because that is what returns the source ids for the connected Stripe, Braintree, Recurly or Chargebee account, and a tenant can have more than one. Auth is a bearer token, with a separate sandbox host for testing so you do not pollute live metrics. The metrics endpoints, including MRR, ARR and churn, are recomputed on a schedule rather than live, so a figure pulled here will not always match what the processor shows for the same minute, and that mismatch is the usual first support ticket. Writes are deliberately narrow: annotations and customer attributes are settable, but subscriptions and charges are owned by the upstream processor. fastn holds each customer's token, keeps the source-id mapping straight and maintains the connection as tokens are rotated.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Baremetrics account so your dashboard shows their MRR and churn without you touching their Stripe keys
Pull the customers and subscriptions list to match your app's accounts against paying subscribers
Trigger a workflow when a customer's plan changes or a charge fails, using the charges feed
Write annotations back to Baremetrics so pricing changes and campaigns are marked on the customer's own metric charts
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to summarise which plans drove last month's net MRR movement for one tenant
Have an agent list subscriptions cancelling this month and draft an internal handover note
Let an agent post an annotation for a pricing change, with the write audited per tenant against that tenant's own token
Example prompt
What was our net MRR change last month, and which plan lost the most?
Set up Baremetrics in 4 steps
- 01Enable the Baremetrics connector from your fastn dashboard.
- 02Have each customer authorise their own Baremetrics account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Baremetrics integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Baremetrics integration without building it. Your customers connect their own Baremetrics account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Baremetrics update is not your on-call problem.
- One integration serves your product and your agents. The same governed Baremetrics connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Baremetrics, across other categories.
NetSuite
Notion
Box
DocusignBaremetrics integration FAQ
How do I add a Baremetrics integration to my product?
Enable the Baremetrics connector in your fastn dashboard, then let each customer authenticate their own Baremetrics account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Baremetrics client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Baremetrics account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Baremetrics account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Baremetrics integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to summarise which plans drove last month's net MRR movement for one tenant
Who maintains the Baremetrics integration?
fastn does. When Baremetrics changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Baremetrics integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Baremetrics integration?
A common starting point: let a customer connect their own Baremetrics account so your dashboard shows their MRR and churn without you touching their Stripe keys. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Baremetrics integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Baremetrics does not change your per-connector cost. You can start free with 3 connected accounts.
Add Baremetrics to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.