Subscription Billing & Revenue Management › Usage Metering

Usage Metering

BC-4250.10 Level 2 Software & Technology 53 providers 84 API surfaces 23 rated strong or better

Ingestion and aggregation of usage events that feed downstream rating and analytics.

Usage Metering (BC-4250.10) is a level-2 business capability under Subscription Billing & Revenue Management in the Software & Technology model. The catalog holds 84 API surface(s) from 53 provider(s) that can perform some part of it, 23 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Usage Event Ingestion BC-4250.10.10

Ingestion of usage events from product services into the metering pipeline.

no catalog coverage

Usage Aggregation BC-4250.10.20

Aggregation of usage events into billable quantities by tenant and meter.

no catalog coverage

Metered Quantity Reconciliation BC-4250.10.30

Reconciliation of metered quantities against source of truth and customer-visible counters.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 10 Complete, well-documented, and agent-ready
OpenAIUsage1 API84.5WSO2Monetization (Collection)1 API83.0KindeBilling Meter Usage1 API82.4OptimizelyImpressions Usage1 API81.3StripeBilling Meters1 API81.1CloudflareBillable UsageBillable Usage V2Usage Analytics3 APIs80.6LeadpingUsage1 API75.4Hive Civilizationbilling-meter1 API74.7DrippayBillable MetricsUsage2 APIs72.3KongMetering EventsMeters2 APIs71.8
Strong 13 Solid coverage with minor gaps
PaidCostsSignalsUsage3 APIs63.1KoyebUsages1 API62.0MoesifBilling Meters1 API61.9Wherobotsusage1 API61.1SolvimoningestmeterPropertiesmeterValueCalculationsmeterValues6 APIs60.7UpsunRecords1 API60.6AppDirectIntegration1 API58.1Platform.shRecords1 API57.9Scanverity Resolution APIResolution usage1 API57.2Tackle.ioMetering1 API57.1LVL LTD COMeter1 API56.4OpenRelayUsage1 API55.2DealHubUsage1 API54.3
Developing 17 Usable, with meaningful gaps to close
SAP BRIM (Billing and Revenue Innovation Management)Usage Events1 API53.430MHzbilling-historybilling-history-details2 APIs52.0MonetizeNowUsage1 API51.8NerdioUsage1 API50.0TogaiEvent IngestionEvent ManagementEvent SchemasUsage Meters4 APIs48.9Pax8Usage LinesUsage Summaries2 APIs48.1KORE Wirelessusage1 API47.4HappyrobotBilling1 API46.2GoliothUsage1 API45.5SugerMetering1 API44.9M3terAggregationCompoundAggregationCounterCounterAdjustments6 APIs44.0TollbitReporting1 API42.1StiggUsage1 API40.9CoreStoryciu1 API40.7Packet HostUsages1 API40.5LagoBillable MetricsEvents2 APIs39.8DatabentoUsage1 API39.5
Thin 10 Limited public surface area
MetronomeBillable MetricsUsage2 APIs37.4PaigoMeasurementsUsage2 APIs34.6OrbEventsMetrics2 APIs33.7BentoMLlago billable metrics1 API32.7Lemon SqueezyCurrentRecordsUsageUsage Records4 APIs32.5OpenMeterEventsMeters2 APIs31.7CacheflowUsage1 API29.8AqueductBill1 API29.5OrdwayUsages1 API28.4HyperlineBillable Events1 API27.3
Emerging 3 Early or largely undocumented
OctaneLive MeasurementsMeasurementsMeters3 APIs25.7RecVueUsage1 API25.1SequenceUsage1 API14.7
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Usage Metering. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →