/v1/decisions, a separate endpoint from chat completions, while still giving you the gateway’s full feature set: authentication, routing, retries, circuit breaking, caching, logging, and cost tracking.
/v1/decisions does not support streaming. Only before-request guardrails apply, scanning the content to judge only (state).Add Provider in Model Catalog
- Go to Model Catalog → Add Provider.
- Select TypeSafe.
- Enter your TypeSafe API key.
- Name your provider (e.g.,
typesafe).
Complete Setup Guide
See all setup options and detailed configuration instructions
Quick Start
TypeSafe uses the Jev request shape:state for the content to judge, and a questions map. Set model to @integration-slug/model. The integration holds the TypeSafe API key, so no provider headers are needed.
cURL
input and a questions array) also works. See Request Shapes.
Question Types
Each entry inquestions picks a type, which determines the shape of its answer:
criteria on a question defines the type-specific detail — for a choice question, the set of labels to choose from.
Model
model defaults to jev-latest if omitted. Pin a specific version (e.g. jev-1.13.0) for reproducible judgments across a TypeSafe model upgrade.
Pricing
TypeSafe bills on input tokens only — output tokens (the typed judgment itself) are free. Usage is reported in the response’susage.input_tokens / usage.output_tokens.
Next Steps
Guardrails for Decisions
Scan
state before it reaches the modelGateway Configs
Add retries, fallbacks, and caching
Observability
Monitor and trace your decisions requests

