Symptom#
pricing_lost (parser_miss) fires on every gemini poll for gemini-3.7-flash (since 2026-10-09) and gemini-3.5-flash (since 2026-10-10). The stored cards are kept by design.
Cause (not a parser bug)#
- The pricing page dropped both ids. https://ai.google.dev/gemini-api/docs/pricing no longer has a section for either one.
parseGeminiPricing works correctly on the live page.
- Google deprecated both models on 2026-10-08. The changelog says
gemini-3.7-flash requests are routed to gemini-3.8-flash, and gemini-3.5-flash requests are routed to gemini-3.6-flash. The models API still lists both ids, so the rows stay live.
- The stored
gemini-3.5-flash card is now stale: $1.50 in / $9.00 out per 1M tokens, while the page prices the successor that actually serves the calls at $0.75 / $3.75. The stored gemini-3.7-flash card happens to match its successor's price.
Decision needed#
For a listed id the provider says is deprecated and routed to a successor, should the adapter:
- price it with the successor's card, sourced from the model page's routing statement plus the successor's price, or
- state
absent: 'cleared' for pricing (the page visibly no longer prices it), or
- something else, e.g. mark the row deprecated from the routing statement?
The ingest maintenance run did not change any code, because each option changes product semantics.
Done when a full poll cycle emits no pricing_lost for these ids and the stored cards match the chosen rule.
Created with PostHog Desktop