
Metronome is a usage-based billing platform, owned by Stripe since January 2026, that meters product events in real time and turns contracts, commits and credits into invoices for AI and infrastructure software companies.
Independently scored, one dimension at a time. Every dimension is sourced, and we say whether a claim is published, reported, or estimated.
Written by the Audit Friendly research team. No vendor edits, no sponsored placement.
You are buying a metering and rating engine. Usage events arrive through an ingest API, SQL or streaming billable metrics turn them into quantities, and rate cards, commits, credits and contract overrides turn those quantities into invoices. Prepaid credit drawdown, enterprise commits with true-ups, seats and hybrid pricing fit in one contract. Stripe says OpenAI, Anthropic and NVIDIA run on it.
The catch is where Metronome stops. It finalizes the invoice, then Stripe, NetSuite or a cloud marketplace delivers it and collects the cash, so dunning, retries and tax run in those systems. Metronome does not create revenue journal entries; finance builds them from data exports or the API, or relies on Stripe, whose docs say it handles revenue recognition for invoices Metronome pushes to it. The NetSuite connector is a public beta. Stripe owns the roadmap and says it will integrate Metronome with Stripe Billing.
Before signing, get the order form in writing: the annual platform fee, the percent of billings, the event rate and any data export or invoice row charges. A consumption commitment is prepaid, non-refundable and expires unused at the end of the term. Ask for the current SOC 1 Type 2 report and its period. Ask whether the NetSuite connector will be generally available before go-live.
Jobs, mapped to how finance teams actually buy.
Forget the 40-row feature grid. Pick a finance workflow and see how this tool and its closest peers actually do it, with our verdict on who wins for whom.
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
Scored on what an outside agent can actually reach: the documented API, how it authenticates, and whether the vendor ships an MCP server.
Exists: Metronome documents no hosted MCP server for billing data, and its documentation index does not mention one (docs.metronome.com, checked 31 October 2026). A first-party local server, @metronome/mcp, was marked deprecated in the Node SDK release of 1 July 2026, and on 27 October 2026 Metronome removed its source and installation instructions from the SDK repository, saying published versions remain available to pin (GitHub changelog, checked 31 October 2026). The public MCP registry lists no Metronome billing server; the two entries named metronome are music tempo tools.
Scope: The deprecated server gave agents a documentation search tool and a code tool that runs scripts against the Metronome SDK, per the SDK changelog, so it could read and write whatever the API token allowed. Metronome now publishes agent skills for Claude Code, Cursor, Codex and similar coding agents. Its skills index lists tasks such as creating a customer, creating a contract from signed order form terms and customer health reviews for account teams; skills that touch data call the API.
Turnkey: Admin-configured. A developer creates an API token, exports it as an environment variable and starts the agent from that shell. Metronome advises a token scoped to read-only access or to the sandbox, since tokens inherit the creator's permissions. There is no OAuth sign-in for agents, and the Stripe Billing review found that the listed methods on Stripe's own hosted MCP server, which Stripe labels public preview, do not cover Metronome contracts or usage data.
In-product AI is about pricing AI products. Billing for LLM tokens, in public preview since 3 September 2026, builds rate cards from token prices that Stripe tracks across 30+ inference providers and applies a configurable markup, per the changelog. No in-product assistant for finance users is documented.
Scalability
Metronome says its infrastructure supports up to 110,000 events a second without pre-aggregation, with a default ingest limit of 5,000 a second and batches of 100 events per request (docs, Usage events at scale, checked 31 October 2026). Stripe names OpenAI, Anthropic and NVIDIA as customers. Rate cards come in 27 listed currencies, and multi-entity billing maps contracts to separate Stripe accounts. The limits that bite first sit downstream: the NetSuite sync is sized for 25,000 arrears invoices a month, and Stripe collapses invoices above 250 line items.
Integrations & data flow
The Stripe link carries the most: Metronome pushes finalized invoices into Stripe and receives payment status back, and Stripe Tax, Avalara and Anrok plug in for tax (docs, Invoice with Stripe, checked 31 October 2026). NetSuite sync of invoices and payments is a public beta, Salesforce receives a daily one-way sync, and AWS, Azure and GCP marketplaces can invoice on the seller's behalf. Data Export feeds Snowflake, BigQuery, Databricks, Redshift, ClickHouse, Postgres and cloud storage; QuickBooks and other systems need a managed or custom integration.
Compliance depth
Metronome announced a SOC 2 Type 2 report in June 2022 and a SOC 1 Type 2 report in February 2023, and says customers get the SOC 1 copy through their representative (metronome.com/blog, checked 31 October 2026). Its docs describe an audit log of every app and API action, readable through an /auditLogs endpoint, three built-in roles plus custom roles, and SAML single sign-on. Points come off because the security page names no data residency options, cites PCI DSS only for its cloud providers, and Metronome leaves revenue journal entries to the customer.
Pricing transparency
Starter is published on metronome.com/pricing at 0.8 percent of billing volume plus $0.04 per 1,000 ingest events (checked 31 October 2026). Custom is quote only, and the pricing model docs explain the order form: an annual platform fee plus charges for billings, events, data export rows and invoice row updates, with a non-refundable consumption commitment that expires unused. Vendr reports a $17,000 a year median but shows no sample size.
Implementation
Since January 2026 a team can open a sandbox from the website, and since June 2026 it can check out to production with a card, per the changelog. The real work is engineering: designing usage events, billable metrics and group keys before go-live, guided by a published go-live checklist. Metronome customer stories cite a few weeks at OpenAI, just over a month at Luminai and a few months at Starburst, all vendor accounts.
Support
Every account names a support contact and raises issues through the in-app support portal (docs, Manage your support contact, checked 31 October 2026). The Custom plan adds a dedicated account manager, enhanced SLAs and priority support, but the pricing page and docs publish no response times. A public status page exists at status.metronome.com. Solutions architects configure paid features such as Custom Reports, per the changelog.
Order-to-cash coverage
Metronome covers metering, rating, contracts, prepaid and postpaid commits, credits, seats, subscriptions, threshold billing and credit memos (docs index, checked 31 October 2026). Invoice delivery, payment collection, dunning and tax run in Stripe, NetSuite or a cloud marketplace. It has no credit management, cash application or deductions, and its revenue recognition guide says it does not create revenue journal entries.
AI / agent readiness
No hosted MCP server for billing data is documented, and the first-party local server, @metronome/mcp, was marked deprecated on 1 July 2026 and removed from the Node SDK repository on 27 October 2026 (GitHub changelog, checked 31 October 2026). Metronome now ships agent skills for coding agents that call its public API with a bearer token, plus SDKs in Python, Node, Go, Ruby and Java. The API itself is complete, with an OpenAPI spec, idempotency keys and webhooks, which keeps the score above API-only tools with thin coverage.
Billing for LLM tokens, in public preview since 3 September 2026, builds billable metrics, products and a rate card from token prices Stripe tracks, then applies your markup. When a provider changes a model price, the rate card updates with the markup kept. It suits a company reselling model inference that cannot hand-maintain token prices.
Prepaid commits burn down in real time, and threshold billing charges the card when a balance falls below a set level. A Metronome video says Salad cut fraud from 15 to 20 percent to under 1 percent; that is a vendor-published customer outcome. Payment-gated commits release credits only after payment succeeds.
Luminai's customer story says contract setup fell from 2 hours to under 5 minutes per customer, and month-end book closing from 2 to 3 hours per customer to under 3 hours in total. These are figures from Metronome's own story page. Revenue journal entries still have to be built from exports.
Raw events go to the ingest endpoint in batches of 100, and SQL or streaming billable metrics aggregate them, so product teams do not pre-aggregate usage. The default limit is 5,000 events a second and rises on request. Stripe's own comparison page recommends Metronome over basic usage billing for high-volume ingestion.
Metronome can send metered usage to AWS, Azure and GCP marketplaces for billing, with GCP added on 3 November 2025, per the changelog. One rate card can then price self-serve, enterprise and marketplace deals. Marketplace invoicing sits on the Custom plan, per the pricing page.
Automate Your Billing Workflows With Metronome's Lifecycle Notifications
A 7-minute technical walkthrough of customer lifecycle notifications with offset logic, used to time trial, renewal and balance messages without polling, per its description. It matters to teams that tie collections nudges or renewals to billing events. Posted 18 September 2025 with about 5,800 views; it is vendor content for engineers. Transcript not read.
Use Metronome to Prevent Billing Fraud With Prepaid Credits
A 7-minute walkthrough of prepaid credits with auto-recharge, which the description says helped Salad cut fraud from 15 to 20 percent to under 1 percent. Prepaid models move cash forward, which a controller cares about. Posted 11 August 2025 with about 3,200 views; the outcome figures are vendor-claimed. Transcript not read.
Usage-Based Billing Tutorial | Episode 6: Contracts and Invoices
An 11-minute tutorial that connects customers to rate cards through contracts and shows Metronome generating invoices from them, per its description. A billing operations lead sees the contract-to-invoice path finance will audit. Posted 27 September 2025 with about 61,000 views; it is vendor training aimed at developers. Transcript not read.
Billing models with Metronome (Stripe Tour London)
A 9-minute session from Stripe Tour London in which a Stripe billing solutions architect covers updates to the Stripe revenue suite and demos Metronome, per its description. It shows how Stripe now positions Metronome next to Stripe Billing. Posted 20 July 2026 with about 9,200 views; it is owner content. Transcript not read.
Token billing for LLM apps | live demo with Metronome + Stripe
A 14-minute live demo of billing for LLM tokens, in which a Stripe engineering manager shows how rate cards follow model prices across providers, per its description. It is the clearest current look at the AI pricing feature. Posted 30 October 2026 with about 34,000 views; Stripe owns Metronome, so this is vendor content about a preview feature. Transcript not read.
Usage-based pricing for AI companies | Inside Metronome
A 2-minute office-visit profile in which Metronome's chief executive describes the platform for usage-based pricing, per its description. It gives context on the team Stripe bought. Posted 21 April 2026 with about 240 views; it is a friendly profile by an independent host. Transcript not read.
Metronome CTO Argues Product Experience Should Include Billing
A 34-second interview clip in which Metronome's chief technology officer argues that customers need real-time cost visibility instead of invoices produced downstream in a back office, per its description. It frames why usage billing lands on the product team as well as finance. Posted 16 September 2026 with about 290 views; a business media channel made it. Transcript not read.
Sara Conlon on How OpenAI is Designing Monetization for the AI Era
A 34-second clip in which an OpenAI speaker describes the monetization building blocks her team built, per its description. OpenAI is Metronome's best-known customer, which makes the clip relevant to AI buyers. Posted 6 November 2025 with about 320 views; it is vendor-published and short on detail. Transcript not read.
Scaling Monetization From PLG to SLG at HubSpot with Sam Lee, Head of Pricing Strategy
A 59-second clip in which HubSpot's head of pricing strategy describes moving monetization from product-led to sales-led motions and the team conflicts hybrid models create, per its description. HubSpot is a named Metronome customer, so this is a buyer voice. Posted 6 November 2025 with about 75,000 views; it was published by the vendor. Transcript not read.
Metronome CEO Scott Woody on The Current State of Monetization
A 40-second clip in which Metronome's chief executive gives three principles for consumption pricing: predictable, visible and controllable spend, per its description. It explains why the product puts real-time spend visibility in front of customers. Posted 6 November 2025 with about 390,000 views; it is vendor marketing about pricing strategy. Transcript not read.
Compliance depth
SOC 1 Type 2 and SOC 2 Type 2 reports on request; an API-readable audit log of every action, three roles plus custom roles, SAML SSO; no revenue journal entries.
Scalability
Supports up to 110,000 events a second, default 5,000; 27 currencies; NetSuite sync sized for 25,000 arrears invoices a month; Stripe caps invoices at 250 lines.
AI / agent readiness
No hosted MCP; its local npm MCP server is marked deprecated. Agent skills and SDKs in five languages reach the full API with a scoped bearer token.
Support
Support portal and a named support contact on every account; Custom adds a dedicated account manager, enhanced SLAs and priority support; no published response times.
Implementation
Self-serve sandbox and card checkout since 2026; engineers design events and metrics first. Customer stories cite a few weeks (OpenAI) to a few months (Starburst).
Pricing transparency
Published Starter: 0.8 percent of billings plus $0.04 per 1,000 events. Custom adds an annual platform fee; Vendr reports a $17,000 a year median.
Order-to-cash coverage
Metering, rating, contracts, commits, credits, seats and credit memos; Stripe, NetSuite or a marketplace delivers and collects; no dunning or revenue entries of its own.
Integrations & data flow
Stripe invoice push with payment status back, NetSuite in public beta, daily one-way Salesforce sync, AWS, Azure and GCP marketplaces, Snowflake and BigQuery exports.
AF Score
Audit Friendly score for Metronome across eight dimensions, 2 November 2026.
Starter rate
Published Starter fee on billing volume, plus $0.04 per 1,000 ingest events (checked 31 October 2026).
Event throughput
Events a second Metronome says its infrastructure supports; the default ingest limit is 5,000 a second (docs, checked 31 October 2026).
Starter
Self-serve with a card. Real-time metering and alerting, usage, seat, subscription and hybrid pricing, native Stripe integration and embeddable billing dashboards.
Custom
Everything in Starter plus Salesforce, NetSuite and AWS, Azure and GCP marketplace invoicing integrations, warehouse data exports, a dedicated account manager and enhanced SLAs.
Annual platform fee (Custom)
A fixed yearly fee for access, separate from consumption charges; it does not count toward any consumption category.
Data Export
Billed on rows written to your warehouse. Snapshot tables recount every row on each sync, and premium tables cover draft invoices, breakdowns and rated events.
Custom Reports
CSV datasets configured by a Metronome solutions architect, described in the changelog as a paid feature.
Stripe payment processing
Charged by Stripe, not Metronome, when Stripe collects Metronome invoices; domestic card and ACH Direct Debit rates shown.
Unused commitment expires
Metronome's pricing model docs say a consumption commitment is a prepaid, non-refundable minimum against consumption charges, and any unused portion expires at the end of the initial or renewal term without refund or credit (checked 31 October 2026). The annual platform fee sits on top and does not count toward the commitment. Size the commitment from trailing billings and event volume, and negotiate rollover in writing if growth is uncertain.
NetSuite sync is still a beta
The NetSuite integration docs say it is in public beta and breaking changes may occur before general availability (checked 31 October 2026). It is sized for up to 25,000 arrears invoices a month, does not support custom currencies or account hierarchy, and needs a standard NetSuite configuration. Metronome says it will not modify the integration for custom NetSuite instances, so those changes fall on the customer.
Revenue entries are yours to build
The revenue recognition guide states that Metronome does not create revenue journal entries (docs, checked 31 October 2026). Finance teams query data exports or the API for deferred and accrued revenue and post entries in the ERP or a revenue subledger. Stripe's docs say Stripe handles revenue recognition for invoices Metronome pushes to Stripe; confirm which Stripe product that needs and what it costs. Prepaid expirations and true-ups need their own treatment, which the guide walks through.
Stripe invoice limits shape the bill
Metronome's Stripe docs list three limits: invoices above 250 line items collapse into one line, decimal quantities are set to 1 with the true quantity moved into the description, and invoices above Stripe's $999,999.99 charge maximum error out unless Stripe raises the limit (checked 31 October 2026). Plan invoice presentation and a usage dashboard so enterprise customers can still audit their bill.
Stripe owns the roadmap
Stripe completed the acquisition in January 2026: Metronome's own post dated 13 January 2026 says the deal closed that day, and Stripe announced it on 14 January 2026, when its chief executive said Stripe looks forward to integrating the capabilities with Stripe Billing (stripe.com/newsroom). Metronome's Legal Center now links its Terms of Service to the Stripe Services Agreement and its privacy policy to Stripe's (metronome.com/legal, checked 31 October 2026). Stripe's comparison page shows Metronome without Connect, Adaptive Pricing, Workflows or Stripe Dashboard support, with limited Checkout support (checked 31 October 2026). Ask how pricing, contracts and the product name will change over the term.
Billing for LLM tokens enters public preview
Rate cards can now be built from token prices Stripe tracks across 30+ inference providers, with a configurable markup that survives provider price changes.
Metronome appears in Stripe onboarding
New Stripe merchants who say they need usage-based billing are now directed to Metronome during Stripe setup, through the Metronome Stripe App.
Self-checkout to production goes live
A user can now sign up, run the onboarding wizard and check out to a production environment with a credit card, without talking to sales.
NetSuite integration opens as a public beta
Metronome syncs finalized invoices and payments to NetSuite for billing or revenue workflows; payment status flows back when NetSuite marks an invoice paid.
Stripe announces it has completed the Metronome acquisition
Stripe announced the close of the deal agreed in December 2025, a day after Metronome's own completion post of 13 January 2026, and said it will integrate Metronome with Stripe Billing. Terms were not disclosed.
Invoicing through Google Cloud Marketplace
GCP joined AWS and Azure as a marketplace Metronome can invoice through, so one rating engine can sit behind all three cloud channels.
On Starter, the bill follows two published rates: 0.8 percent of billings and $0.04 per 1,000 ingest events (metronome.com/pricing, checked 31 October 2026). A company billing $250,000 a month and sending 50 million events a month pays about $2,000 for billings plus $2,000 for events, so roughly $4,000 a month or $48,000 a year. That is an Audit Friendly calculation from the published rates.
Custom contracts are quoted as an annual platform fee plus consumption charges. Vendr reports a $17,000 a year median for Metronome purchases, with no sample size or billing volume shown, so it cannot be set against the Starter math above (vendr.com, checked 31 October 2026). Stripe payment processing is billed separately by Stripe.
Custom order forms carry an annual platform fee, and any consumption commitment is prepaid, non-refundable and expires unused at the end of the term (pricing model docs, checked 31 October 2026). Metronome's Legal Center now links its Terms of Service to the Stripe Services Agreement (metronome.com/legal, checked 31 October 2026). Term length, renewal uplift and termination rights for an order form are not on public pages; ask for the order form and the governing terms before signing.
Data leaves through the API and through Data Export, which syncs contracts, finalized invoices, payments, customers and events to Snowflake, BigQuery, Databricks, Redshift, ClickHouse, Postgres or cloud storage. Data Export is listed on the Custom plan and billed per row exported. Invoices pushed to Stripe or NetSuite also live in those systems.
Metronome publishes no standard timeline. Its customer stories cite a few weeks for OpenAI, just over a month for Luminai and a few months for Starburst, all vendor accounts. A sandbox opens from the website, and Starter customers can check out to production with a card.
Engineers do most of the work: event design, billable metrics, webhooks and the Stripe or NetSuite link. A pricing or revenue operations lead builds rate cards and contracts, and the controller maps invoices to the ledger. Custom accounts work with Metronome solutions architects.
Partly. There is no hosted MCP server, and the first-party local MCP package on npm is marked deprecated. Metronome instead publishes agent skills that let coding agents such as Claude Code create customers and contracts and review commit health through the public API.
Setup is manual: a developer creates an API token, ideally scoped to read-only or the sandbox, and exports it to the agent's shell. Collection, dunning and revenue entries sit in Stripe or the ERP, so an agent working in Metronome cannot complete them.
Answered only from our own published research on this tool, never from general internet noise. If we cannot answer it well, our research agents will dig in and publish a sourced answer.