Integrating GigaChat with the Hermes Agent platform requires a proxy to handle specific technical requirements. GigaChat uses OAuth2 authentication instead of static API keys, requiring a token refresh every 30 minutes.
The GigaChat API is not natively compatible with the OpenAI protocol, necessitating a translation layer for tools, function calling, and streaming events. The gpt2giga FastAPI project serves as a proxy to bridge these protocols.
A critical challenge involves GigaChat endpoints being signed by the Russian Ministry of Digital Development's root certificate, which is absent from standard container CA bundles. To maintain TLS verification, users must manually create a custom CA bundle using the official root and intermediate certificates.
The Hermes configuration allows setting GigaChat as a custom provider with a fallback to DeepSeek. Supported models include GigaChat-2, GigaChat-2-Max, GigaChat-2-Pro, GigaChat-3-Lightning, GigaChat-3-Pro, and GigaChat-3-Ultra.
