Docs
CommunityJev Integrations & Adapters
MLflow AI Gateway Jev Providers
MLflow's AI Gateway lists TypeSafe Jev among its evaluation providers: a typesafe passthrough at /gateway/typesafe/v1/systemone forwards raw System One requests using the server-side TypeSafe key, separate from MLflow judges.
- Format
- Docs
- Reading time
- 2 min
- Published by
- Community
- Author
- MLflow
- Last verified
- Oct 2026
- Languages
- Python
- Capabilities
- Self-hostedRequires API key
Highlights
- The TypeSafe passthrough is POST /systemone under http://localhost:5000/gateway/typesafe/v1, forwarding to https://api.typesafe.ai/v1 by default.
- OpenRouter's Jev decision models share the /gateway/typesafe/v1/systemone route; typesafe/jev-router is a chat model on normal chat routes.
- The gateway endpoint name goes in the request body's model field, and the gateway attaches its server-side TypeSafe API key.
- Jev routes support only structured System One evaluation, not the gateway's chat, embeddings, OpenAI-compatible, or streaming APIs.
- The curl example asks a noul whether state.outputs answers the question in state.inputs, under the model name jev-evaluator.
Watch out
Vendor documentation for MLflow's AI Gateway, which runs on localhost with LiteLLM available only as an optional extra. It shows no Jev pricing, licence, or rate limits, and it warns that the raw System One route is not a chat endpoint and must not be passed to make_judge as a gateway model.
Questions about this entry
Short answers drawn from the linked project or page.
As evaluation providers: TypeSafe and OpenRouter Jev decision models both use the /gateway/typesafe/v1/systemone passthrough, which forwards structured System One evaluation requests with the gateway's server-side TypeSafe API key.
POST to http://localhost:5000/gateway/typesafe/v1/systemone with the endpoint name in the model field. Requests go to https://api.typesafe.ai/v1 by default, and a proxy or another System One host can be set through api_base.
No. TypeSafe and OpenRouter Jev decision endpoints support only structured System One evaluation requests; the gateway's chat, embeddings, OpenAI-compatible, and streaming APIs are not available through this route.
TypeSafe gateway endpoints are raw System One endpoints, separate from MLflow judges created with make_judge(model='typesafe:/...'). Do not pass a TypeSafe gateway endpoint as model='gateway:/...' to make_judge.
The gateway endpoint name goes in the request body's model field, and the gateway forwards the request to the configured TypeSafe model. The example uses jev-evaluator for an answer-quality noul over state.inputs and state.outputs.
No. MLflow AI Gateway supports many providers natively; LiteLLM can optionally be installed to extend the gateway to providers not listed, but it is not a dependency and Jev support does not require it.
No. The page lists TypeSafe and OpenRouter as evaluation providers with the /systemone passthrough and gives curl and SDK examples, but includes no pricing, model aliases, or rate limits and no benchmark information.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: Jev 1.14 is now on OpenRouter
X: Jev lands on the Vercel AI Gateway
X: Jev as an LLM guardrail inside Agentgateway
YouTube: Greg Isenberg and Ryan Vogel on the businesses Jev unlocks, and a path in through the Vercel AI Gateway.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.