Pricing content should help developers understand the structure of model costs before asking them to compare every provider detail.
What the first version should do
The public pricing page should stay static, conservative, and SEO friendly. It can explain model route, usage unit, billing layer, and cost visibility without claiming unverified lowest prices.
Where deeper pricing belongs
Live SKU tables, discounts, usage ledger views, and calculators belong in a later logged-in pricing tool or model detail surface.