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 70 API surface(s) from 45 provider(s) that can perform some part of it, 17 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
8
Complete, well-documented, and agent-ready
Strong
9
Solid coverage with minor gaps
Developing
17
Usable, with meaningful gaps to close
Thin
10
Limited public surface area
Emerging
1
Early or largely undocumented
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 →