Tresor AI
Tresor AI
Changelog
  • Docs
  • Changelog
  • Feature requests
  • Support portal

Tresor AI changelog

One reasoning dial everywhere

One reasoning dial everywhere

You can now control reasoning the same way across supported Tresor routes. Instead of learning provider-specific flags for each upstream, send one reasoning value and Tresor translates it behind the scenes for the route that actually serves the request.

This is the main upgrade: reasoning effort is now unified at the Tresor layer. That makes it easier to move between providers, use automatic routing, and keep failover plans without rewriting request logic whenever a model sits behind a different upstream contract.

One request shape, clearer control

  • One public reasoning knob — Prefer "reasoning": "high" or "reasoning": "off" instead of provider-native controls. The object form still works for compatibility.

  • One shared effort ladder — Tresor accepts the same public reasoning-effort values across supported routes and maps them route by route.

  • Route-aware discovery — GET /v1/models?detail=true now shows each route's verified supported_efforts and default_effort, so you can see what is actually available before you send traffic.

  • Safer routing — When one route cannot satisfy the requested reasoning setting, Tresor can still choose another compatible route for the same logical model.

Reasoning text now comes back in the new reasoning fields: message.reasoning for non-streaming responses and delta.reasoning for streaming responses.

reasoning_content still works as a compatibility alias for now, but it will be deprecated on 2026-09-01. If you read reasoning traces today, switch to reasoning now and you will not need another migration later.

Learn more at docs.tresor.co/guides/reasoning-controls

Kimi K3 is now available

The second big update in this release is Kimi K3. It is the latest open-source frontier model in the API, and it gives you another top-tier option when you want strong general intelligence without moving away from the OSS side of the model landscape.

  • A new high-end OSS option — Kimi K3 is now available in the Tresor API model lineup.

  • Frontier-level intelligence — In practice, it belongs in the same conversation as the latest Anthropic and OpenAI models on hard, multi-step work.

  • Same API ergonomics from day one — Kimi K3 fits into the same routing layer, receipts flow, and unified reasoning controls described above.

As always, the privacy model does not change with any of this. You get the same zero-access guarantees, with a simpler API contract on top.