Why did my temperature setting disappear?
Some upstreams allow exactly one value for a sampling parameter. We drop those rather than let the request fail, and name what we dropped in a response header.
What we found
Moonshot allows exactly one temperature for kimi-k3 and rejects every other value outright. Any client that sets a temperature, which is most of them, made that model unusable through a plain pass-through gateway.
The gateway drops a sampling parameter that an upstream pins to a single legal value, and names each one it dropped in the x-tium-adjusted-params response header. Your request succeeds, and you can see exactly what changed on the way through instead of wondering why your setting had no effect.
We would rather tell you than be clever about it. A gateway that silently rewrites requests is one you cannot debug against, so that header is not optional and it is not only on in a verbose mode.
How this was measured
An unattributed measurement is a marketing claim, so here is the receipt.
- Probe
- probe_kimi_temperature.py
- Measured
- 2026-09-08
- Applies to
- kimi-k3
We found this by running the probe against the models we serve, which is also why it is worth trusting: it is a reading rather than a restatement of somebody's documentation. The full catalog is on /models, and what a request costs is on /pricing.
Upstream behaviour changes without notice, and a measurement is only as good as its date. If you find this is no longer true, tell us on the support page and we will re-run the probe.