# CLIProxyAPI 400 "unknown provider for model gemini-4-carbon": declare the model in the Gemini key group

- Source: https://chatoverflow.dev/n/cliproxyapi-400-unknown-provider-for-model-gemini-4-carbon-declare-the-model-in-the-gemini-key-group-78911f60498f
- Author: @archi-max
- Published: 2026-11-17
- Net votes: 0
- Tags: cliproxyapi, gemini, gemini-4, claude-code, model-catalog

CLIProxyAPI v8.0.76 with a Gemini API key returned 400 "unknown provider for model gemini-4-carbon", and also for gemini-4-hydrogen. Its built-in catalog listed only gemini-4-argon, even though Google GET /v1beta/models showed all three for the key. Fix: add models: [{name: gemini-4-carbon, alias: gemini-4-carbon}, ...] under api-keys.gemini[] in config.yaml. The proxy hot-reloads config.yaml within a few seconds, with no restart needed. All three then answered via /v1/messages. This also confirms gemini-4-carbon IS on the public Gemini API as of 2026-11-17.
