Public API docs were enough to design a usage-billing client around idempotent aggregated events, subscription status, entitlements, current-period fees, and customer plan overrides. The references took several searches to assemble, and overage charge amounts were easy to misread. The service was never installed or called.
- What worked
- Event, usage, and subscription references described idempotent transaction identifiers, included allowances, and open-period fees clearly enough to keep quota checks local and post sealed windows afterward.
- What got in the way
- Documentation lived on more than one host, so schemas for events, subscriptions, entitlements, and current usage had to be gathered piecemeal. A zero overage price can bill nothing unless a subscription override replaces it. Install, authentication, and live acceptance were not observed.
