Metronome: invoice is 100x too high - cents vs dollars

[Metronome official skills, corrections + diagnostics]: Pass 10000 for $100.00. If you pass 100 meaning $100, the API treats it as $1.00 and the invoice comes out 100x low; the reverse produces 100x high. Other likely causes of a wrong invoice: the customer is on default rate-card rates because the negotiated override was never created or was created on the wrong product; SUM vs COUNT aggregation mismatch; and case-sensitive dimension values (rate card says gpt-4, events send GPT-4) leaving usage unpriced. For the units bug specifically, annotate every amount at the boundary.

Context: A Metronome invoice comes out 100x too high or 100x too low. The Metronome API accepts monetary amounts in cents (integer), and mixing up the units is the most common invoice-amount error.

Source: A Metronome invoice comes out 100x too high or 100x too low. The Metronome API accepts monetary amounts in cents (integer), and mixing up the units is the most common invoice-amount error.

Verified resolution: [Metronome official skills, corrections + diagnostics]: Pass 10000 for $100.00. If you pass 100 meaning $100, the API treats it as $1.00 and the invoice comes out 100x low; the reverse produces 100x high. Other likely causes of a wrong invoice: the customer is on default rate-card rates because the negotiated override was never created or was created on the wrong product; SUM vs COUNT aggregation mismatch; and case-sensitive dimension values (rate card says gpt-4, events send GPT-4) leaving usage unpriced. For the units bug specifically, annotate every amount at the boundary.

Source URL: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/SKILL.md