01
Idempotent usage
Each event carries an externalId. Retried requests are counted as duplicates, not billed twice.
Solutions
Token or credit based products need metered billing that does not punish customers for retried requests.
The problem
AI usage is bursty and request-level. Without idempotent metering, retries inflate bills and support has to explain the difference.
01
Each event carries an externalId. Retried requests are counted as duplicates, not billed twice.
02
Price per unit, by graduated tier or by volume, with minimum and maximum amount guardrails.
03
Per-subscription usage summaries show current-period quantities and amount before the invoice is issued.
Resources involved
Each item is a documented API resource with a dashboard view and a permission that gates it.
What the beta covers for this model
Anything outside this list should be confirmed with us before you plan around it. Beta scope is documented, not implied.
Tell us how you charge and which provider you use. We will confirm the fit before you integrate.