Skip to main content

​
September 9, 2026

Documentation correction: top_k is silently disabled at low temperature
  • top_k has no effect unless temperature is 0.001 or above. Below that threshold, including when you omit temperature entirely, top_k is forced to 1 and decoding is greedy. A request carrying top_k: 40 and no temperature returns argmax, and nothing in the response says the value was ignored
  • Measured on gemma-4-31B-it, 8 runs of one prompt: top_k: 40 without temperature gave 1 distinct output, the same request with temperature: 1.0 gave 8
  • Documented the defaults applied when you omit a sampling parameter: temperature 0.0, top_p 1.0, top_k 1048576, repetition_penalty 1.0
  • top_k must be 1 or greater. -1 and 0 are rejected with a 400 on /v1/chat/completions and /v1/messages. They are accepted on /v1/responses, which does not validate the lower bound, but they do not mean “unrestricted” anywhere. The API reference stated a maximum of 100 for top_k; no upper bound is enforced
  • The byte-identical output you get when you omit temperature is not a pinned seed. It is the forced top_k of 1. Do not rely on it across releases
  • Documented why MiniMax-M2.7 samples while the other models decode greedily: on the MiniMax bundles only, unset sampling parameters are backfilled from the checkpoint’s own generation_config.json
  • Action: set temperature explicitly before you tune top_k. See How top_k interacts with temperature
Platform maintenance release: vision tool calling, reasoning token counts, error envelope
  • Vision requests now support tools and structured output. gemma-4-31B-it honours tools, tool_choice and response_format on requests that carry an image. The constraint is applied during generation. See Vision
  • Reasoning token counts are reported on every EU model. Read usage.completion_tokens_details.reasoning_tokens to budget and bill reasoning separately from the visible answer. It was previously null on gemma-4-31B-it. See Counting reasoning tokens
  • Malformed image data returns HTTP 400, not 500. This is a permanent error. Do not retry it
  • Errors use a consistent JSON envelope, with two exceptions. The response carries a request_id you should quote in every support report. A malformed image and an unhonoured forced tool_choice still return a flat shape where error is a string. See API error codes
  • Streaming tool calls on gpt-oss-120b are clean. No reasoning scaffolding leaks into delta.content. Note that the same model adds a channel field to the delta on streams with no tools - ignore delta fields you do not recognise. See Streaming tool calls
  • Documentation corrections: the audio page listed stream_options as an accepted parameter. The endpoint rejects it with HTTP 400. response_format honours only json and text; verbose_json, srt and vtt are accepted but return plain text. See Audio

​
August 18, 2026

Documentation correction: temperature has no default
  • The API reference stated a default temperature of 0.7 on /v1/chat/completions and /v1/responses. That default does not exist. The claim is removed from the OpenAPI spec and from every page that repeated it
  • Omit temperature and gemma-4-31B-it, gpt-oss-120b, DeepSeek-V3.2, and Meta-Llama-3.3-70B-Instruct decode greedily. MiniMax-M2.7 samples. The same applies on /v1/chat/completions, /v1/responses, and /v1/messages
  • Greedy decoding is the setting most likely to send a reasoning model into a non-terminating repetition loop, so requests that set no sampling parameters were exposed to the failure the docs warned about
  • /v1/messages differs from the Anthropic API, which documents a temperature default of 1.0. Code ported from the Anthropic SDK switches to greedy decoding unless you set the parameter
  • Action: set temperature explicitly on every request. See If you omit temperature

​
July 16, 2026

Deprecation: MiniMax-M2.5 retired

​
July 3, 2026

Upcoming Deprecation: MiniMax-M2.5
  • MiniMax-M2.5 will be deprecated on July 16, 2026 at 9:00 PM CEST
  • Recommended replacements: MiniMax-M2.7 (complex reasoning, 192k context) or gemma-4-31B-it (cost-efficient, vision-capable)
  • Both replacement models are already live - migrate before July 16th to avoid service disruption
  • See deprecations for migration guidance

​
June 20, 2026

Model Update: Gemma 4 replaces Gemma 3
  • gemma-3-12b-it has been removed and replaced by gemma-4-31B-it in a single switchover. Requests to gemma-3-12b-it are no longer served - update your integrations to use the gemma-4-31B-it model ID
  • Gemma 4 is EU-hosted on Infercom’s sovereign infrastructure with full data sovereignty, offering a 128k context window and improved performance while maintaining vision support
  • Vision guide updated with gemma-4-31B-it examples
  • Rate limits and deprecations updated

​
June 5, 2026

New Models: Whisper-Large-v3 and E5-Mistral-7B-Instruct
  • Whisper-Large-v3 is now available for audio transcription and translation - OpenAI’s state-of-the-art ASR model, EU-hosted with full data sovereignty
  • E5-Mistral-7B-Instruct is now available for generating embeddings - high-quality vector representations for RAG, search, and classification workflows
  • Both models run on EU sovereign infrastructure with no data leaving EU jurisdiction
  • Rate limits updated for both models
  • Model overview updated with new embedding and audio model sections

​
May 24, 2026

Anthropic SDK Compatibility
  • New /v1/messages endpoint for Anthropic SDK compatibility
  • Use the Anthropic Python SDK with Infercom models - just change the base URL
  • Supports streaming, system prompts, multi-turn conversations, and tool use
  • Documentation

​
May 22, 2026

New Model: MiniMax-M2.7
  • MiniMax-M2.7 is now available as an EU-hosted model with 192K context window
  • Recommended for agentic coding workflows - replaces M2.5 as the default recommendation
  • MiniMax-M2.5 (160K context) remains available but will be deprecated in a future release
  • Rate limits updated for MiniMax-M2.7

​
May 15, 2026

Responses API
  • New POST /v1/responses endpoint for agentic workflows - supports function tools, streaming, and reasoning effort control
  • Compatible with OpenAI Responses API standard
  • Supported models: MiniMax-M2.7, MiniMax-M2.5, gpt-oss-120b
  • Documentation
Model Update
  • gemma-3-12b-it moved to EU sovereign infrastructure - first vision-capable model with full EU data sovereignty
  • Vision guide
New Integration
  • Codex CLI now supported via Responses API
  • Updated Cline and OpenCode guides with Plan/Execute configuration pattern

​
April 24, 2026

Model Catalog Updates
  • DeepSeek-V3.1 moved to Global Model Catalog: Now served via proxy (US region) instead of EU-hosted infrastructure
  • gemma-3-12b-it added: Google’s Gemma 3 12B model now available via Global Model Catalog (Japan). This is the first vision-capable model on Infercom — see Vision guide
  • DeepSeek-V3.2 context length corrected: Updated from 8k to 32k tokens
  • EU-hosted models: MiniMax-M2.5 and gpt-oss-120b remain as the sovereign EU options
Documentation Updates

​
April 6, 2026

New Documentation: Agentic Coding

​
April 3, 2026

Global Model Catalog Streamlined
  • Reduced Global Model Catalog to 2 models: Meta-Llama-3.3-70B-Instruct (128k) and DeepSeek-V3.2 (8k)
  • 8 models deprecated: Qwen3-32B, Qwen3-235B, DeepSeek-R1-0528, DeepSeek-R1-Distill-Llama-70B, DeepSeek-V3-0324, DeepSeek-V3.1-Terminus, Llama-4-Maverick-17B-128E-Instruct, Meta-Llama-3.1-8B-Instruct
  • See deprecations for migration guidance
  • Fixed MiniMax-M2.5 context length to 160k (was incorrectly listed as 164k)

​
March 12, 2026

Model Update: MiniMax M2.5 replaces Meta-Llama-3.3-70B-Instruct
  • MiniMax M2.5 is now available as an EU-hosted model on Infercom’s sovereign infrastructure in Germany
  • Meta-Llama-3.3-70B-Instruct has been deprecated and removed from the platform. See deprecations for migration guidance
  • Rate limits updated for MiniMax M2.5

​
February 27, 2026

Global Model Catalog Launch
  • 9 new models available through the Global Model Catalog, including DeepSeek-R1-0528, Qwen3-235B, Llama-4-Maverick, and more
  • EU-hosted and globally-routed models are now clearly separated in the model overview
  • Rate limits updated for all 12 models across Free and Developer tiers
  • API sn_metadata now returns is_external and region fields for all models

​
February 14, 2026

New Documentation
  • Added Performance & Latency guide covering connection pooling, response performance metadata, streaming optimization, and best practices for minimizing latency

​
February 5, 2026

Documentation for Global Model Catalog
  • Added documentation for the Global Model Catalog, covering EU-hosted and globally-routed models
  • Documented how to identify model regions via the API (sn_metadata.region) and the Playground
  • Updated API reference with sn_metadata schema and ?verbose=true query parameter
  • Reviewed and qualified sovereignty claims across documentation to reflect Global Model Catalog

​
January 23, 2026

Model Update
  • Updated DeepSeek model from DeepSeek-V3-0324-cb to DeepSeek-V3.1 with expanded 128k context window
  • The previous model has been deprecated and is listed on the deprecations page
  • Updated rate limits for all models

​
January 13, 2026

New Improvements
  • Documentation cleanup and link fixes

​
December 30, 2025

Updated the model catalog to reflect currently available models on Infercom Inference Service. The model list and rate limits documentation have been updated accordingly.

​
November 17, 2025

We are pleased to announce the launch of Infercom’s documentation portal. This comprehensive documentation has been created based on SambaNova’s documentation (dated October 7, 2025) and adapted for Infercom’s EU sovereign AI inference platform. Key features
  • Complete API reference documentation with OpenAI-compatible endpoints.
  • Developer guides for integrating with Infercom’s inference platform.
  • Model catalog and configuration documentation for all supported models.
  • Platform architecture and deployment guides.
  • Usage examples in Python and TypeScript, powered by OpenAI-compatible SDKs.
All documentation will be continuously updated to reflect Infercom-specific features, European data sovereignty capabilities, and platform enhancements as they become available.