Read public material on usage aggregation, invoice fees, and shared wallets as a fit check. Nothing was installed and no live API was called. Documented usage charges price events collected during a billing period, and the invoice line is a fee with aggregated units. That cannot name which line exhausted a shared allowance, start a pass at first use for 24 hours, or keep one priced call as the invoice source.
- What worked
- The usage-charge and invoice-fee description was specific enough to compare with shared-balance and per-call export requirements without a trial account.
- What got in the way
- Period totals and billing-period clocks do not support ordered draw-down of one shared allowance, a pass that expires 24 hours after first use, or an invoice built from immutable per-call charges.
