Commerce & Payments · Integration
Metronome
Add Metronome to your product for your customers, and give your AI agents governed access to it.
Embed a Metronome integration so usage measured in your product turns into a bill in the customer's own Metronome account, and so your product can show a running total before the period closes. Usage events are sent with idempotency, which is the requirement in usage-based billing: a retry after a timeout must not double-count. Plans, commits, credits and draft invoices are read per tenant, so a customer sees their own pricing rather than a generic estimate, and a spend threshold or a new invoice can trigger entitlement and alerting steps as the event lands. fastn owns the credentials, retries and API upkeep, and the same connection serves your AI agents.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Send usage events from your product into a customer's Metronome account so metered charges come from what actually happened.
Read a customer's plans and draft invoices so your product can show a running bill before the period closes.
React to a spend threshold or a new invoice with an event trigger so entitlement and alerting run immediately.
Support each customer's own pricing, commits and credits as per-tenant configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent explains a customer's current spend by reading their own usage and draft invoice.
An agent reports which accounts are tracking over their commit, with each read audited.
An agent submits a usage correction within scoped permissions and idempotently, so a retry cannot double-count.
Example prompt
What is this customer's Metronome spend so far this period, and which usage is driving it?
Set up Metronome in 4 steps
- 01Enable the Metronome connector in your fastn dashboard.
- 02Have each customer authorise their own Metronome account so calls run under their credentials.
- 03Map the usage events, plans and invoice fields your product uses, then enable triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Metronome integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Metronome integration without building it. Your customers connect their own Metronome 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 Metronome update is not your on-call problem.
- One integration serves your product and your agents. The same governed Metronome 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
Chargebee
StripeOften used alongside
Tools the same teams tend to run next to Metronome, across other categories.
NetSuite
Notion
Box
DocusignMetronome integration FAQ
How do I add a Metronome integration to my product?
Enable the Metronome connector in your fastn dashboard, then let each customer authenticate their own Metronome account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Metronome client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Metronome account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Metronome 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 Metronome integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent explains a customer's current spend by reading their own usage and draft invoice.
Who maintains the Metronome integration?
fastn does. When Metronome 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 Metronome 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 Metronome integration?
A common starting point: send usage events from your product into a customer's Metronome account so metered charges come from what actually happened. 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 Metronome integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Metronome does not change your per-connector cost. You can start free with 3 connected accounts.
Add Metronome to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.