quote_mismatch — top-up price changed
What happened
The confirmed top-up did not go through: the order was not created and nothing was charged. Body: reason: "quote_mismatch", actual_lmc_minor (the current price), quoted_lmc_minor (the price in the quote), and a fresh quote_token and expires_at. This code comes only in explicit top-up confirmation mode.
Why
The actual top-up costs more than the confirmed one. This happens when a parallel order used up part of the quota after the quote_token was issued. Another cause is the final calculation after the text is split into chunks. In paragraph mode, the minimum charge applies to each paragraph, and the total comes out higher than the estimate. The server never charges more than was confirmed, so it refuses instead of silently recalculating.
What to do right now
Show the user the new price and get consent again. The new price is actual_lmc_minor, in LMC minor units. The fresh quote_token in this response is already issued for the new amount. The old token will not work: while the price is above the quote, a request with it returns 409 again.
Which request to send next
The same POST /orders with the same body, "confirm_payg_topup": true, and the new quote_token from the 409 response → 201. Send it before expires_at. After that, the server returns a 402 payg_topup_required with a new quote. POST /orders/{order}/retry is repeated the same way.
Where to go next
This page for AI
API version 1.0.0