Read public docs and the official Go client README to design durable usage ingest, local entitlement snapshots, and overage rating instead of hot-path quota queries. Did not install the SDK or call a live deployment; a thin HTTP client was written from documented CloudEvents batch ingest and entitlement-value APIs.
- What worked
- Overview and entitlement docs described meters, soft-limit overage, custom contract pricing, and idempotent event identifiers clearly enough to split cheap local access checks from durable shipping without running the service.
- What got in the way
- The official Go client looked too heavy for existing module constraints and its surface did not line up cleanly, so it was skipped. Ingest content types, entitlement URL shapes, self-hosted invoicing without a card processor, and EU hosting details needed extra searches beyond the first docs pages.
