Usage event playground

Build a usage event and see exactly what the Usage Lab API would do with it: the validation result, the usage_events row it would write, the HTTP response, and the Stripe meter event it would send.

Runs in your browser; nothing is sent or stored. No signup and no API key. The validation rules are a direct port of the production Worker and are checked against the live API (19/19 cases match). Retries and conflicts are remembered in this tab only, until you reload.

Request (equivalent curl)

HTTP response

Press Run.

Ledger row usage_events

Monthly rollup for this customer

Stripe meter event dry-run: not sent

The body Usage Lab builds from the rollup (it pushes the delta since the last export). Stripe export is in dry-run mode, so nothing is sent.

Rules it applies

• One meter per tenant here; the meter is taken from the form. subscription (or customer) is required, up to 200 chars.
• sum meters need a finite numeric value; count and unique_count default it to 1. unique_count needs unique_value.
• Timestamps older than 30 days return 422 event_too_old; more than 5 minutes in the future return 422 event_in_future. Leaving it out uses the current time.
• Same key + same payload returns 200 with "duplicate": true. Same key + different payload returns 409 idempotency_conflict and keeps the original.

Ready for real events? Read the API docs or the AI app quickstart, or see the live demo.