I opened Lago's charge-grouping guide and searched its documentation for wallets, graduated tiers, taxes, and whether usage keeps the price in force at event time after a rate change. That material supported a comparison during platform selection. The evaluation stayed on public docs; there was no install and no API call.
- What worked
- The grouping guide was reachable and addressed invoice lines broken out by a property, which was the first question for dimensional usage.
- What got in the way
- Tier scope, prepaid drawdown, and historical price retention each needed a separate search. One guide page did not present a single contract model covering effective-dated rates, volume thresholds, and credit balances together.
