requests meter when created. This meter is the only meter in the system — it tracks all billable request activity and powers limit enforcement, usage billing, and analytics.
How Meters Work
- Each provider gets a
requestsmeter automatically — no configuration needed - Your application records usage via the SDK, NATS, or automatically through MCP tool calls
- Other systems consume the data — plans enforce limits, billing calculates costs, dashboards visualize trends
Meter Fields
The requests Meter
Every provider automatically receives a requests meter when their account is created:
This meter is auto-configured per provider and cannot be archived. It is seeded idempotently — creating a provider multiple times is safe.
Aggregation
Therequests meter uses count aggregation, which counts each usage record as one unit. SolvaPay also supports sum aggregation for meters that accumulate numeric values (e.g. tokens consumed), though only the requests meter is currently in use.
How Meters Connect to Plans
Usage-based and hybrid plans specifymeasures: 'requests', which links them to the provider’s auto-assigned requests meter. This link enables:
- Limit enforcement — the plan’s
limitfield sets a hard cap on the meter’s aggregated value per billing period - Free units — the plan’s
freeUnitsfield defines how many units are included before billing starts - Usage billing — at end-of-period, the meter’s aggregated value determines the billable amount
Next Steps
- Usage Records — recording and querying usage data
- Plans — how plans reference meters for billing and limits
- Billing — end-of-period usage billing