Compared this billing ledger from public guides and then implemented an HTTP usage-ingest client from the documented event API, with no live account. Two meters, customer and subscription references, and idempotent event ids mapped cleanly to overage invoicing, but the ingest payload had to be assembled from several overlapping pages.
- What worked
- The event and meter guides were enough to design list ingest for request and egress rollups, including stable event references so retries are duplicates rather than new charges. Public material also presented EU residency and bank-transfer invoicing as native capabilities, which matched the required billing model.
- What got in the way
- The exact ingest-list contract was not in one place. Field names, number-value shapes, and endpoint choice were pieced together from concept, meter, troubleshooting, and OpenAPI pages after repeated searches, which slowed setup even though the API itself was never called live.
