Enabled per organizationUsage-based billing must be enabled for your organization before these endpoints accept requests. Contact your Yuno account manager to enable it. Requests from an organization where it is not enabled return
403 PRODUCT_NOT_ENABLED.Attributes
A meter is a named, countable action your product performs — tokens generated, API requests served, gigabytes held. It defines theevent_name your systems send on every usage event and how those events aggregate into a quantity per billing cycle. A meter carries no price of its own until it is attached to a plan as a metered price; default_price is only a convenience default for USD plans.
The unique identifier of the meter (MAX 64; MIN 36).Example: 55555555-5555-5555-5555-555555555555
The unique identifier of the account that owns the meter (MAX 64; MIN 36).Example: 00000000-0000-4000-8000-000000000002
The meter display name (MAX 255; MIN 3). Leading and trailing spaces are trimmed.Example: AI tokens
What the meter counts and how it is reported. Optional;
null when not set.Example: LLM tokens consumed by model responses, reported once per responseThe key your systems send on every usage event to reference this meter (MAX 100). Lowercase letters, digits,
_ and . only (^[a-z0-9_.]+$). Unique per account across all meters, ACTIVE or INACTIVE — creating another meter with the same event_name is rejected with 409 METER_EVENT_NAME_CONFLICT, even if the existing one is archived. Immutable after creation; a PATCH that includes it is silently ignored.Example: ai_tokensHow reported events roll up into the cycle quantity. Immutable after creation; a PATCH that includes it is silently ignored.Possible values:
SUM= Adds thevalueof every event in the cycle. Use for consumption: tokens, minutes, messages, deliveries.COUNT= Counts events, ignoringvalue(each event counts as 1). Use for per-call pricing: API requests, jobs.LAST= Keeps the most recentvaluereported in the cycle (byoccurred_at). Use for gauges: gigabytes held, seats in use.
Singular label of the unit the meter counts, used when usage is displayed. Optional.Example: token
Optional default price per unit beyond the included credits. Inherited by USD plans that attach this meter without an explicit
price_per_credit. null when not set.Key-value pairs attached to the meter (MAX 48 entries; keys unique per meter). Independent of the
metadata you send on usage events.Status of the meter. Always
ACTIVE on creation — a status sent to Create Meter is ignored.Possible values:ACTIVE= The meter accepts usage events and can be attached to plans.INACTIVE= Archived. Usage events for itsevent_nameare rejected with400 METER_NOT_FOUND, it cannot be attached to plans, and its existing metered prices are frozen. Theevent_namestays reserved. Set through Update Meter and reversible (status: ACTIVE); there is no delete.
Related
- Create Meter
- Retrieve Meter
- List Meters
- Update Meter
- Report Usage Event
- The Metered Price Object — how a meter is priced on a plan
- Usage-Based Billing guide