[unionai-docsy-agent]

What changed in the product

The October 2026 release notes (#1929) announce structured decisions on the Inference Gateway. POST /v1/decisions takes a state and named questions and returns a typed answer for each. TypeSafe models, hosted LLMs, and Union-served vLLM/SGLang apps with Answers decisions turned on can answer these requests. Until now the docs mention the endpoint only once, as the Answers decisions toggle in Providers. Linear DOC-1576 asks for docs on calling the endpoint, linked from Decision models.

Changes, page by page

• New: content/user-guide/inference/inference-gateway/decisions.md (Union only, weight 7):
  • a curl example, followed by what to put in each placeholder (gateway endpoint, virtual key, a model the typesafe provider allows)
  • how to reach the endpoint behind Union sign-in (flyte proxy app, then http://127.0.0.1:8600), with a link to Use from your laptop
  • when the console shows the filled-in command: only when the gateway has a deployed typesafe provider, or a vLLM/SGLang provider with Answers decisions on
  • the request fields (model, state, questions)
  • the two question kinds that can be traced to source: noul → a probability, and choice → one of the options, with criteria mapping each option to a description
  • which providers answer decisions: typesafe; hosted chat models that support tool calling (the gateway asks through one forced tool call); vLLM/SGLang apps only with Answers decisions on
  • a gateway on an older image may not serve /v1/decisions; if the overview shows an update available, redeploy
• inference-gateway/providers.md: the Answers decisions row now links to the new page.
• inference-gateway/_index.md: adds a Decisions entry to "In this section".
• decision-models/_index.md: adds a Related link to the new page. The link is wrapped in {{< variant union >}} because this page builds for both variants and the gateway page is Union only.

Evidence

Every claim on the page was checked against Union's internal source (the console's gateway settings, the gateway's provider list, and the gateway API definitions). The page's example request copies the body of the decisions command the console generates. The rules for which providers answer decisions come from the gateway API's own description of the decisions setting. The answer types in the intro (probability, choice, score) come from the console's description of the endpoint and the release notes.

Nothing was run, and no call was made to /v1/decisions, so none of the endpoint's runtime behavior is confirmed by a call.

Left out because it couldn't be verified

• The response JSON shape. The page says only what kind of answer each question gets. It gives no field names. An example response is needed.
• The request format for score questions. The console's example shows only noul and choice. The intro still says an answer can be a score, based on the console's description of the endpoint and the release notes.
• Whether budgets, rate limits, model allowlists and guardrails apply to decisions calls. The guardrail envelope in flyteplugins-union lists request_type: decisions, but how the gateway enforces these wasn't confirmed.
• The gateway image version that first serves /v1/decisions, and what an older gateway returns for it. The page says only that an older image may lack the endpoint and that redeploying updates it.

Open questions for the reviewer

No listed owner covers the Inference Gateway, so these questions aren't addressed to anyone.

• What does a /v1/decisions response look like? How is a score question written (its kind and the shape of its criteria)?
• Does every hosted provider in the supported list answer decisions, or only chat models that support tool calling? The API definition says hosted providers answer "by the same emulation" (one forced tool call), so the page states the tool-calling condition. That needs confirming, especially for non-chat providers such as elevenlabs and runway.
• Do virtual-key budgets, rate limits, model allowlists and guardrails apply to decisions calls the way they do to chat traffic?
• Which gateway image version first serves /v1/decisions, and what does an older gateway return for it (a 404)?

Pre-flight review

Docsy's reviewer read this draft before it was opened and found 9 problems to fix. The draft was amended for them (2 declined, with evidence the check accepted), and a check of the amendment found nothing left to fix.

Its optional suggestions, which the page doesn't need to be right; take them or not:

• content/user-guide/inference/inference-gateway/decisions.md line 11: The intro says an answer can be "a score", but the kind table (lines 53–56) documents only noul and choice. A reader can't write a question that returns a score. The page also gives no example response, so a reader can't tell which field holds each answer. Document the score kind and the response shape, or remove "or a score" until they can be documented.

---

Docsy case 3588: https://docsy.apps.demo.hosted.unionai.cloud/cases/3588

_{Drafted by Docsy, Union.ai's documentation agent, from the product changes and requests in this case. Review it like any PR; close it if it's not wanted.}

[github-actions]

GHA build & deploy preview

Built by .github/workflows/build-pr.yml and deployed to the docs CF Pages project by .github/workflows/deploy-pr-preview.yml.

Branch alias	https://pr-1939-docsy-case-3588.docs-dog.pages.dev
This commit	https://8b063351.docs-dog.pages.dev
Commit SHA	5237a769d12623d1ab9710cef5c1de692d573dfa

Updated automatically on every push.

[unionai-docsy-agent]

Docsy actions: what Docsy did on this PR, and at whose direction. Docsy adds a line for each.

• 2026-11-09 13:51 UTC · merged it (squash), after marking it ready for review, without an approving review · at the direction of Peeter Piegaze (ppiegaze)

[Copilot]

🔵 Needs a closer look

The gateway implementation and API definitions are unavailable, and no endpoint call verifies the request contract or hosted-provider tool-calling compatibility, so gateway-owner confirmation is needed before publication.

No open issues 🎉

What changed in this PR

Documents POST /v1/decisions as a way to ask typed questions through the Inference Gateway, and connects the new guide to existing inference documentation.

Changes:

• Adds a request example, field descriptions, provider requirements, and guidance for local access and gateway updates.
• Links the guide from the gateway overview and provider settings.
• Adds a Union-only link from Decision models, preserving Flyte variant visibility.

File	Description
content/​user-guide/​inference/​inference-gateway/​providers.md	Links Answers decisions to the new guide.
content/​user-guide/​inference/​inference-gateway/​decisions.md	Documents endpoint usage, question kinds, and supported providers.
content/​user-guide/​inference/​inference-gateway/​_index.md	Adds Decisions to the section overview.
content/​user-guide/​inference/​decision-models/​_index.md	Adds a Union-only related link to gateway decisions.

_{Review effort: Balanced}