mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-17 15:24:19 +00:00
PRICE_TABLE carries a :batch row at half price and the committee projection quoted it as the tier a real run should use. Nothing submits batch work. Every caller reaches the model through provider.chat, which posts to the synchronous generateContent endpoint, so the batch row had exactly one consumer and that consumer was a projection. The consequence was not cosmetic: a spend approval was made on the batch figure and the real charge would have been twice it. A price nothing can pay is worse than no price, because it reads as the cheaper of two available choices rather than as an absent feature. The row stays as a note on what the tier would cost, with the reason no projection may quote it, so the next person to reach for it adds the submission path in the same change that starts pricing it.