How to Use Jev AI: 7 Access Routes & Working Code
A battle-tested engineering guide to obtaining API keys, selecting the lowest-latency access route, installing SDKs, and deploying 4 copy-paste production recipes.
Need RLCD mathematical proofs & System One architecture? Read our TypeSafe Jev Deep Dive HubTL;DR — 5-Bullet Executive Summary
- • What it is:TypeSafe Jev is a non-autoregressive decision model built for structured boolean, choice, and score outputs in 70–500ms without text hallucinations.
- • Fastest access:Create an early-access key on TypeSafe Console ($5 free credit), or route via Vercel AI Gateway / OpenRouter for instant evaluation.
- • Minimal call:Send unstructured text via
POST https://api.typesafe.ai/v1/systemonewith typed questions; results return in ~100ms. - • Pricing math:Billed at $0.042 per 1M input tokens. Parallel question output sampling is free, costing ~$0.00004 per decision.
- • Critical limit:64k combined token window, pure text input (no multimodal audio/vision), and zero ungrounded world-knowledge generation.
Where to Access Jev: 7 Routes Compared
Detailed breakdown separating direct official providers from cloud aggregators and self-hosted orchestration proxies.
| Route | Key / Auth Method | Pricing & Terms | Best Used For | Action |
|---|---|---|---|---|
TypeSafe Direct Official Direct API | TypeSafe API Key (via console.typesafe.ai/settings/keys) | $0.042 / 1M input tokens, free output; new accounts get $5 creditsCurrently early access with invite waitlist rolling out continuously. | Production workloads demanding lowest latency (~100ms) and direct access to jev-1.13 / jev-latest. | Visit |
Vercel AI Gateway Managed Cloud Gateway | Vercel AI Gateway Key (model: typesafe-ai/jev) | Free until Sep 25; standard Vercel token billing applies afterwardPromotional zero-cost trial closes September 25; ideal for immediate zero-friction evaluation. | Next.js & Edge applications deployed on Vercel wanting unified observability and edge caching. | Visit |
Lovable AI Gateway Managed Cloud Gateway | Lovable Platform Gateway Token | Free until Sep 27, 23:59 UTC; standard platform tier thereafterFree window active until Sep 27, 23:59 UTC. Best for quick no-config trial runs. | Rapid prototyping and teams already building within Lovable visual harnesses. | Visit |
OpenRouter Unified Router | OpenRouter API Key (model: typesafe/jev-latest or typesafe/jev-1.13) | Per-request gateway pricing (~$0.042/M input, 32K context window)Check real-time rates at openrouter.ai/models as proxy pricing may adjust. | Multi-model A/B evaluation, automated benchmarking vs GPT/Claude judges, and centralized key management. | Visit |
Requesty Unified Router | Requesty Gateway Key | Pass-through list price ($0.042/1M input) + analytics overheadIdeal for teams requiring enterprise compliance and audit trails for automated decisions. | Enterprise logging, circuit breakers, fallback cascades to LLMs, and team usage tracking. | Visit |
LiteLLM Proxy Self-Hosted Orchestration | Own TypeSafe API Key (passed through self-hosted proxy) | Open-source software; pay only your direct TypeSafe upstream usageRequires running a LiteLLM container with TYPESAFE_API_KEY injected in environment. | Self-hosted infrastructure where internal microservices consume a unified OpenAI-compatible endpoint. | Visit |
Pydantic AI Type-Safe Framework | Own TypeSafe API Key (via TypeSafeModel provider) | Open-source library; calls TypeSafe API directly at list pricePairs Jev's discrete output space with Python's typing system for compile-time safety. | Python engineers wanting declarative question models, schema validation, and IDE auto-completion. | Visit |
10-Minute Quickstart (Python & TS)
Install SDKs, configure your environment, and send your first typed decision call.
# 1. Install official SDK
# pip install typesafe-sdk
import os
from typesafe_sdk import TypeSafeClient, Noul
# 2. Initialize authenticated client
client = TypeSafeClient(api_key=os.environ.get("TYPESAFE_API_KEY"))
# 3. Dispatch System One decision call
result = client.system_one(
model="jev-latest",
state="Customer message: Please cancel and refund my subscription immediately. This is ridiculous.",
questions={
"is_urgent": Noul(instructions="Does this message require immediate attention within 1 hour?")
}
)
# 4. Result is an empirical calibrated float [0.0 - 1.0]
urgency_prob = result.answers["is_urgent"].noul
print(f"Urgency probability: {urgency_prob:.2f}")
if urgency_prob > 0.80:
print("Action: Auto-escalate to priority manager")4 Copy-Paste Production Recipes
Tested architectural patterns addressing common high-frequency automation bottlenecks.
Support Ticket 3-Way Triage (Dual Noul with Ambiguity Gate)
Enterprise customer support routing: Automatically separate urgent human escalation requests from automated bot-solvable queries, while flagging ambiguous borderline queries for tier-1 human review.
Traditional LLMs take 2–4 seconds and frequently hallucinate department categories. Jev evaluates both boolean conditions in parallel (~100ms) with mathematically calibrated probability thresholds, costing $0.00004 per ticket.
import os
from typesafe_sdk import TypeSafeClient, Noul, NoulCriteria
# Define discrete evaluation criteria with explicit boundary definitions
SUPPORT_QUESTIONS = {
"is_human_escalation": Noul(
instructions="Is the customer explicitly demanding or requesting to speak with a human agent or supervisor?",
criteria=NoulCriteria(
true="Customer mentions speaking to a human, agent, person, manager, or representative",
false="Customer asks general technical or billing questions without demanding human takeover",
),
),
"is_repeat_contact": Noul(
instructions="Has the customer indicated they previously reached out about this unresolved problem?",
criteria=NoulCriteria(
true="Explicitly mentions prior tickets, multiple attempts, or prolonged waiting on an ongoing issue",
false="First-time inquiry or no indication of past interactions",
),
),
}
# Calibrated decision thresholds
CONFIDENCE_HIGH = 0.80
CONFIDENCE_LOW = 0.20
def route_support_ticket(message: str) -> dict:
"""Evaluates ticket state and dispatches deterministic routing instructions."""
api_key = os.environ.get("TYPESAFE_API_KEY")
with TypeSafeClient(api_key=api_key) as client:
result = client.system_one(
model="jev-latest",
state=message,
questions=SUPPORT_QUESTIONS
)
wants_human = result.answers["is_human_escalation"].noul
is_repeat = result.answers["is_repeat_contact"].noul
# Ambiguity Gate: If probability is uncertain (between 0.20 and 0.80), route to triage queue
if CONFIDENCE_LOW < wants_human < CONFIDENCE_HIGH or CONFIDENCE_LOW < is_repeat < CONFIDENCE_HIGH:
return {
"route": "manual_triage_review",
"reason": "Calibrated score falls in uncertainty band",
"scores": {"wants_human": wants_human, "is_repeat": is_repeat}
}
priority = "p0_urgent" if is_repeat >= CONFIDENCE_HIGH else "p2_normal"
target = "senior_human_queue" if wants_human >= CONFIDENCE_HIGH else "ai_automated_responder"
return {
"route": target,
"priority": priority,
"scores": {"wants_human": wants_human, "is_repeat": is_repeat}
}"I have messaged your team three times since Tuesday and my invoice is still wrong. Can someone please actually look at this?"
{"route": "senior_human_queue", "priority": "p0_urgent", "scores": {"wants_human": 0.99, "is_repeat": 0.96}}
Raise CONFIDENCE_HIGH to 0.90 if human agent capacity is severely constrained. Lower CONFIDENCE_HIGH to 0.70 for VIP customer tiers where false negatives (missing an angry customer) are expensive.
Jev does not synthesize the email reply itself. Use Jev strictly to route the workflow, then invoke GPT/Claude to draft the response if routed to the AI bot.
Jev Question Types & Gotchas Quick-Ref
Understand the exact signatures and avoid subtle schema mistakes.
Noul
Noul(instructions="...", criteria=NoulCriteria(true="...", false="..."))
Choice
Choice(instructions="...", criteria=["Option A", "Option B", ...])
Score
Score(instructions="...", criteria=["Level 0 scenario", "Level 1 scenario", "Level 2 scenario"])
Integration & Operational FAQs
Direct, practical answers regarding keys, SDK capabilities, and architectural limits.
Ready to explore the mathematical architecture?
Learn about RLCD calibration, speculative fan-out sampling, and Kahneman System One mechanics.
