Real-time usage governance for Metronome
Metronome bills it. Schematic enforces it in your product: entitlements, usage controls, and the billing experience customers see, as an SDK.
● Live · what your customers see. Hover a callout, click a row.
Every event counted live at scale. Same usage Metronome rates.
Who gets what, live, per plan, seat, and agent.
Per-seat and per-agent caps stop runaway agents before the invoice.
Every grant and burn, append-only, export-ready.
One financial-grade pool across people, teams, and agents.
One-off grants and overrides, no engineering ticket.
Self-serve top-ups, with auto top-up rules the buyer sets, priced from the Metronome rate card.
Contracts, commits, rate cards, and invoices stay in Metronome. The wallet shows the same numbers.
Trusted in production by:
Adding usage-based pricing to your product is easy. Enforcing it is much harder.
Schematic for Metronome is built to sell, enforce, and grow usage revenue.
Entitlements and billing in one loop, so you can run usage revenue end to end.
Runtime enforcement from the ledger that bills.
One check gates the feature from the ledger Metronome invoices, so UI and API always agree.
- One call returns allow or deny. Your app never needs a customer’s billing state.
- Millisecond decisions. Every check and meter event streams back live.
- Sales-led and self-serve alike. Overrides, custom plans, and trials, enforced the same way.
import { useSchematicEntitlement } from "@schematichq/schematic-react"const { value, featureUsage, featureAllocation } =useSchematicEntitlement("ai-search")return value ? <Search used={featureUsage} of={featureAllocation} /> : <Upsell />
Metered credits that turn limits into expansion.
Usage meters live in credits, and every limit offers more credits, a higher cap, or an upgrade.
- Leases and reservations. Reserve, commit what’s used, release the rest. No double-spending across concurrent agents.
- One-click top-ups. Credit packs priced on your Metronome rate card, booked as commits on the contract.
- Zero-hour provisioning. Upgrades and rep overrides take effect the moment the customer says yes.
Usage governance, set once and enforced everywhere.
Spend caps per company, user, or agent, with a warning first. Live on save, no deploy or ticket.
- Cap any dimension. Company, seat, or autonomous agent, from hourly to monthly.
- Warn before you stop. Thresholds alert the buyer and your team before the cap.
- Change it in production. Policies are data. Finance and customer success change them, no engineer.
Metronome bills it. Schematic enforces it.
Metronome owns the contract, rate card, and invoice. Every check, cap, override, and top-up passes through Schematic, so access never drifts from billing.
Every feature check and metered event flows through one SDK call, in React, Node, Python, or Go.
Entitlements, caps, credits, and overrides answer allow or deny in milliseconds and write the ledger.
The same usage drives the rate card, the invoice, and the drawdown on the commit.
Provisioning, expansion, collections, and integrity agents read balances and take action through the MCP.
Runtime enforcement, not webhooks
Webhooks report a limit after it’s crossed. A runtime check answers locally, before the feature runs.
- Checks run in-process on local entitlement state. No round trip.
- Plan, cap, and override changes reach every SDK in seconds, in order.
- Credit leases decide high-volume checks locally, with no double-spending across workers.
- On a network blip, the SDK uses last-known state and buffers usage.
- Every check needs a billing API round trip or a cache you maintain.
- Deliveries arrive out of order or twice. You dedupe and reorder them.
- Miss one, and customers keep access they shouldn’t or lose access they paid for.
- Someone maintains the receiver, queue, idempotency keys, and nightly reconciliation.
Enterprise-grade infrastructure you and your engineers can trust.
No single point of failure on the request path. Enforcement never breaks a feature.
Local-first checks
An in-process cache, so the network can’t slow or fail a check.
Layered caching
Every check reads the nearest copy: in-process, edge, or region.
Replicated state
Replicated across regions from one ledger. A regional outage changes nothing.
Graceful degradation
Per-feature fallback: allow, deny, or last-known state. Usage buffers, the ledger stays exact.
An operating system for monetization.
Own the entitlements and the catalog Metronome bills, and run round-the-clock revenue agents for your customers on one ledger.
Expansion agent
Turns limits into upgrades.
Flags accounts near their limits and drafts the upgrade offer, with an override ready for the rep.
Usage changes daily.
CRO · Customer success
- 1Find accounts near their limit read
find_companies_near_limit(threshold: 85%)3 companies above 85% · Northwind at 96% - 2Read the usage read
get_feature_usage(northwind, 30d)ai.search +48% month over month · 4 of 4 seats at cap - 3Draft the offer enforce
create_custom_plan(northwind, from: growth, credits: +25k)Offer drafted · $2,400/mo · ready for review - 4Hand it to the rep send
notify(owner: j.reyes, channel: slack)Rep pinged with the usage brief and a one-click override
Built for the AI era.
Usage governance, through MCP. Set it up in an afternoon, then ask and act in plain language.
From prompt to enforced usage, inside your editor.
Describe your pricing to Claude, Cursor, or Codex. Plans, the entitlement check, and the wallet land in your code, mapped to Metronome.
Usage, balances, limits, contracts, answered from the ledger.
Find accounts near limits, grant overrides, schedule plan changes, all from the ledger Metronome bills against.
Read balances, grant credits, cap limits, provision plans.
Your agents get these tools too. Every action lands in the ledger, audit trail included.
- check_companies_usage
- get_feature_usage
- find_companies_near_limit
- set_company_override
- remove_company_override
- create_custom_plan
- get_company_plan
- create_credit
- publish_plan_version
- list_company_overrides
Schematic MCP server · REST API · SDKs for React, Node, Python, Go, Ruby, Java, PHP, and .NET · webhooks
Entitlements are commercial infrastructure.
Commercial agility, developer experience, and customer trust all rest on the entitlement layer under your billing.
Package your product to win deals and drive growth.
Custom plans for sales-led deals, self-serve tiers for everyone else, and packaging changes that ship without a deploy.
Buy the entitlement system instead of building it.
Your app never needs to know the billing state of a customer. One call returns allow or deny, and the entitlement infrastructure around your billing tool never gets built.
Deliver customer trust structurally.
Detailed invoicing, clear usage caps, fair-use alerting policies, and a customer-facing wallet, all powered by the Entitlements API.
The architecture engineers pick.
“Using Schematic means our engineers can focus on building product features rather than maintaining billing logic.”
“The industry is going to look back and wonder why the heck we ever asked internal teams to build these capabilities, often poorly, and over and over.”
“It's Schematic versus, in my opinion, being dumb and building it. I know companies that are putting so much development work into their billing platforms. Why? You shouldn't build anything that isn't your product.”
Works out of the box with Metronome.
The native integration starts enforcing the catalog you defined in Metronome.