Used the official documentation to select m3ter and implemented an OAuth-authenticated, idempotent usage-export client and outbox around its ingestion API. The product modeled commitments, expiring credits, graduated tiers, effective-dated pricing, currencies, and rerating well, but no tenant was available for a live end-to-end call.
- What worked
- The documented billing concepts closely matched the required contract terms. Reusing each source event identifier as the measurement UID supported a straightforward retry-safe outbox design, and the bill lifecycle and balance documentation was useful for defining operational controls.
- What got in the way
- Several focused documentation searches were needed to establish ingestion limits, EU residency, late-usage behavior, and historical bill handling. Credentials, an EU tenant, and provisioned contracts were unavailable, so API reliability and the final production configuration were not validated.
