Composite event
A single tracked event (one vevee.track call) that, via match rules, increments more than one limit group at the same time. The default model in AIPricingLab.
Last updated: 2026-05-10
Definition
Real billing models are not 1:1. One image render might count toward "total renders this month" AND "premium renders this month" AND "cost in cents." Instead of three separate track calls, AIPricingLab fires one event and routes it through the match rules of every limit group on the user's plan. All matching groups increment atomically. This is composability that naive metering tools lack.
Example
vevee.track(userId, "image.render", 1, { model: "flux-pro" }) increments lg_total_renders, lg_premium_renders, AND lg_cost_cents (each with the appropriate quantity).
Related terms
Limit group
The basic unit of quota in AIPricingLab: a label, a unit, a quota, a period, and a list of match rules that decide which events count toward it.
Glossaryreserve / commit / release
The atomic three-step pattern that gates AI calls under concurrency: reserve atomically holds quota with a 60s TTL; commit confirms after the call succeeds; release rolls back on error.
GlossaryTokens
The unit of input and output for large language models - roughly 0.75 of a word in English. LLM providers price by tokens; metering AI apps usually does too.