vust

API guide · checked 2026-08-08

GigaChat API: What Actually Works

A live-smoke compatibility map: token exchange, visible IDs, where schema/functions/files/vision/SSE work, and where the contract differs across v1, v2 and models. This does not claim GigaChat is routed into VUST products.

4 chat models · 4 embedding IDs · checked 2026-08-08Independent guide; no live VUST integration claimed
Open VUST AI (not GigaChat)
OAuth token ~30 minutes; explicit scope required4 chat + 4 embedding IDs in the live catalogJSON Schema, functions, files, vision and SSE smoke-tested

Minimum safe contract

  1. Authorization Key → OAuth with explicit scope → cache the access token for roughly 30 minutes.
  2. Trust the Russian CA; never use insecure TLS.
  3. Validate JSON/functions and normalize v1/v2/SSE separately.
  4. Treat entitlement, limits and cost as runtime facts, not /models promises.

Functions and limits

JobValidated pathCaveat
JSON/files/visionGigaChat-2-MaxStill validate the schema
FunctionsGigaChat-2-ProValidator is schema-sensitive
v1/v2/SSEGigaChat-3-UltraDifferent response shapes
text2imageGigaChat-2Returned file must be downloaded

FAQ

How does GigaChat API authentication work?

GIGACHAT_API is an Authorization Key, not a reusable access token. Exchange it at the OAuth endpoint with an explicit PERS, B2B or CORP scope, then cache the returned access token for its roughly 30-minute lifetime. Load the Ministry Russian Trusted Root CA and never disable TLS verification.

Which GigaChat models were visible in the live catalog?

On 2026-08-08 the personal-scope catalog returned GigaChat-2, GigaChat-2-Pro, GigaChat-2-Max and GigaChat-3-Ultra, plus Embeddings, Embeddings-2, EmbeddingsGigaR and GigaEmbeddings-3B-2025-09. Catalog visibility is not entitlement proof: the tested account returned 402 for every embedder.

Which advanced functions passed a smoke test?

Max passed strict JSON Schema, file reading and exact Russian banner vision; Pro passed function validation and calling; Ultra passed v1, v2 and SSE; Lite produced a valid downloadable JPEG through text2image. These are dated compatibility results, not a promise that every account has every entitlement.

What integration traps matter most?

Literal natural-language following was unreliable across all four chat models, so validate schema or exact output. v1 and v2 response and SSE shapes differ. /tokens/count worked for Ultra but returned 404 for GigaChat-2 IDs. Caller-managed context remains required; X-Session-ID only enables provider caching.

Does VUST currently route user requests to GigaChat?

No. The repository has a protocol-safe @vust/gigachat candidate package and dated live evidence, but no bot imports it as a production provider. This page documents the API; it is not a claim that /chat or /models uses GigaChat.

Sources: official GigaChat API documentation and VUST's dated compatibility matrix. Repeat /models and task-specific smokes before production: IDs, prices and entitlements drift. Official API overview.