Capability change
- Before: Builders could use hosted gateways for model calls, but these items do not establish access there to the newly reported decision-model options and Decisions API.
- Enabling change: Microsoft-Decision-1 became available in Microsoft Foundry and Vercel AI Gateway; LangSmith documented support for the OpenAI Decisions API.
- After: Builders can access decision-oriented models or APIs through multiple hosted AI gateway offerings.
Human consequence: Teams can evaluate and integrate decision calls through their existing model-access layer instead of relying only on generated text for such choices.
Bottleneck: The reports establish availability and gateway support, not interoperability, performance, or the quality of decisions on a particular task.
Buildability: B2. Verification: source-inspected. Related shift: coding-agent-general-workbench.
The shift is concrete because separate reports place decision-oriented models or APIs in Foundry, Vercel AI Gateway, and LangSmith’s gateway. That offers builders more than a standalone model announcement: decision calls are appearing in existing hosted access layers.
A useful build is a small routing and evaluation layer that compares these decision options against the choices a workflow needs. The items do not show shared semantics or equivalent behavior across providers, so task fit and gateway compatibility remain to be verified.
Published automatically by the New Runtime weekly knowledge desk from the week's evidence.
Supporting evidence
- Microsoft launches Decision-1 model in Foundry (signal, 2026-10-10)
- Decision-1 from @MicrosoftAI is now available on AI Gateway. (signal, 2026-10-10)
- LangSmith LLM Gateway now supports the OpenAI Decisions API. (signal, 2026-10-10)
Provenance
Auto-created by the New Runtime weekly knowledge desk on 2026-10-12 from evidence reviewed in the week of 2026-10-05. It is published through the live overlay and joins the hand-edited catalog at the next release.