Jev directory
CommunityJev Integrations & Adapters
Flow Steward Extension for TypeSafe AI (Jev)
Flow Steward extension that exposes Jev through standard project connections, plus an importable support-triage example. Adds an Evaluate with JEV connector that takes state and named choice, score, or noul questions and returns answers with usage.
- Stars
- 0
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
Highlights
- Evaluate with JEV accepts text, object, or array state plus named choice, score, and noul questions
- Returns model, answers, and usage against the official TypeSafe API contract
- Requests are bounded to 2 MiB and responses to 4 MiB, with no internal retries
- Connection setup picks a default model such as jev-latest and a timeout of 1-60 seconds
- Bundled jev_support_triage example routes messages to billing, technical, sales, or general
Questions about this entry
Short answers drawn from the linked project or page.
Install the release ZIP through Extensions then Install from file, or through the Flow Steward extension catalog. Then open TypeSafe AI, go to Connections, pick a project, name the connection, and enter a key from TypeSafe Console.
The key is stored in that project's encrypted connection secrets; a project can hold several independent connections. The connector resolves the opaque reference at its own authorized boundary, so the key is never passed through Template or an agent prompt.
No. Test connection authenticates with GET /v1/models and does not send a decision request, so passing it does not by itself verify credentials beyond that call.
The graph returns manual_review when category or urgency confidence falls below min_confidence (default 0.7), when the human-required probability reaches human_threshold (default 0.8), or when the category is unrecognized. Manual review is only a routing recommendation; the example creates no ticket, approval task, or notification.
Image and Box questions are outside this version's contract, and compressed responses are unsupported. Jev is not a chat-completion model, so it cannot be added as the LLM behind an agent through Add model.
The connector has no third-party runtime dependencies and does not retry requests internally. Authentication, rate limit, timeout, TLS, transport, and malformed-response errors surface as stable error codes, without raw provider error bodies or credentials.
Yes. Test Run can call TypeSafe and consume provider credits. Importing the example itself makes no API call: it ships disabled and contains no API key, configured secret default, or machine-specific install ID.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
Facebook: Intake Router keeps diagnosis out of the answer space at the front desk.
FacebookClinicnotes
X: OpenRouter Decision Model Rankings
X: herdr + jev, an agent router
X: A group chat bot with decision room routing
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.