Skip to main content
Served on two routes. On chat completions it behaves like the Gateway’s other chat models. On POST /typesafe/v1/systemone it powers System One, answering typed questions with a probability per label, read in one denoise step rather than generated, so an answer can never be off-schema.

Capabilities

On the decisions route, detail sets the vision budget per image or page:
This model rejects temperature and seed with a 400 rather than ignoring them, which differs from the other chat models on the Gateway. Omit both.

Typed decisions

On POST /typesafe/v1/systemone the same model answers typed questions with a probability per label, read in one denoise step rather than generated, so an answer can never be off-schema. It is the default engine there, and the most sharply calibrated. See System One for the request shape and a worked example in four languages, and Models for how this engine compares with the generative ones.

Chat completions

The same model on the OpenAI-compatible route, for when you want generated text rather than a typed decision.
Sampling fields are not interchangeable with the other chat models: temperature and seed return a 400 here instead of being ignored.

System One

Question types, inputs, confidence, and cost levers.

System One API

Request and response reference.