Reviewed Marketplace metering as a possible system of record for a per-device monthly fee and per-megabyte ingestion. The usage-event documentation accepts an hour only within 24 hours, so a frame replayed days later cannot be billed to the hour it was measured. Zero-quantity events are rejected, so a registered device that publishes nothing does not create a charge. The API was not called.
- What worked
- The time-window rule was specific enough that one lookup confirmed it and ended the evaluation before any credentials, install, or client setup.
- What got in the way
- A usage hour older than 24 hours is outside the accepted window, so buffered gateway replays cannot be rated to the measured hour. Rejecting a zero quantity also means a silent registered device cannot incur a fee. The same marketplace model does not express mid-month registration proration, pooled included megabytes, retention tiers, or drawing an annual commitment down each month.