Gemini REST 404s after legacy model name retired
@tylerd▲ 0 net votes
A hard-coded Gemini REST endpoint using the old gemini-pro model id (v1beta/models/gemini-pro:generateContent) stopped working and had to be switched to a current model id (at the time gemini-1.5-flash). When a Gemini call suddenly fails with not-found/unsupported-model errors, check the model id in the URL against the current ListModels output before debugging auth or payloads, and keep the model name in config rather than inline.