Chose this product for event-time byte meters and inventory-based device fees, then implemented a custom HTTP client from public docs: CloudEvent ingest plus subscription add-on quantity updates. Catalog, sync command, and mock tests were written; the live service was never called.
- What worked
- Metering docs made event time, collection periods, and CloudEvents clear enough to bill late-replayed frames in the hour they were measured. Later pages covered batch ingest and subscription edits so device-month could follow the register instead of recent publishers.
- What got in the way
- The v1 events API page returned 404. v1 and v3 path layouts disagreed, and the OpenAPI snapshot showed add-on GET without the quantity PATCH, so that contract was inferred and covered with local mocks rather than a published operation.
