Meter and control every model request
Turn provider JSON into tenant-scoped charge items, then enforce account routes, limits, credits, and overage rules before drift reaches finance.
One metering plane for LLM APIs, agent SaaS, workflow usage, and subscription overages. Give your LLM gateway billing, realtime limit controls, and audit-ready usage evidence in about an hour.
Events stay close to the systems that create them, while every charge item remains tied to immutable billing evidence.
Accept usage JSON from gateways, model providers, agents, and internal services.
Select extractor and pricing versions by tenant, project, and event time.
Run precompiled accessors and pricing programs on the hot path.
Connect Meterry to the usage your product already tracks. Your teams get the billing, reporting, and revenue answers they need without rebuilding the back office around spreadsheets.
Turn product usage into clear invoice details by customer, plan, and line item.
Show each customer what they used, what it cost, and which feature or project drove it.
Know when a customer is nearing included usage, ready for an upgrade, or due for overage billing.
Track billed revenue against AI costs, credits, and discounts before month-end surprises.
Share what your product measures, how it should be priced, and what finance needs to prove.
When this stage enters the viewport, each usage case becomes the active page: AI gateway control, revenue analysis, then subscription overages.
Turn provider JSON into tenant-scoped charge items, then enforce account routes, limits, credits, and overage rules before drift reaches finance.
Finance can compare billed revenue, usage cost, discounts, and customer-level margin from the same immutable usage facts.
Layer plan versions, included quotas, memberships, and metered overages around the usage-rating kernel without burying lifecycle logic in formulas.
Trusted by teams that need pricing changes to be fast, testable, and reversible.
"We replaced pricing spreadsheets and one-off usage scripts with a versioned metering plane that can explain every invoice line."
Keep the metering kernel small, fast, and auditable while product layers evolve around it.
Stop matching invoices against logs after the fact. Store the raw event, selected rule versions, charge items, and exact rating output together.
Compile rules once, then evaluate only metric-specific candidates and generic fallbacks.
Stable metrics are extracted and priced directly. Dynamic metrics use x-billing items and override extractor output for the same metric.
Every event traverses the same compiled pipeline — extract, route, then emit metrics that flow into usage and invoice.
A control plane for product, engineering, finance, and audit to work from the same facts.
Whether you are charging seats, tokens, workflow runs, or compute, Meterry keeps usage and pricing evidence on one plane.
Rule sets are versioned, tested, published, and replayed without changing application code.
Every rule, event, usage record, and charge item is scoped to a tenant.
Meter tokens, requests, tool calls, and agent work without encoding lifecycle logic in CEL.
Trace every invoice line back to raw event payloads, rule versions, and rating outputs.
Join software teams that bill AI usage, agent workflows, and SaaS entitlements from one event-driven revenue plane.