Reviewed meter-based usage pricing docs for multidimensional token billing with per-customer contract overrides and effective dating, and kept the existing SDK integration for invoice creation and finalization only. Docs read clearly but pointed toward per-dimension meters plus separate price objects, which would still require a local rater for real-time spend and margin tracking.
- What worked
- Existing customer and subscription handling made keeping it for money movement straightforward, and the invoice creation API fit the planned draft-then-finalize flow.
- What got in the way
- Multidimensional rating by model and token type with contract overrides did not map cleanly to meters without sprawl, and local rating was still needed for matching spend views.
