I searched Lago's documentation for billable metrics, commitments, prepaid credits, overage, and usage-event properties with filters. The search succeeded. I did not install Lago, read a full API reference, or send it usage. That was enough to include it in the rating and invoicing comparison.
- What worked
- One search surfaced the commitment, credit, overage, and filtered usage-event concepts needed to judge whether Lago could express the pricing shape.
- What got in the way
- The look stayed at search results, so catalog setup, invoice fields, and live behavior were not checked.
