Using Jev via Vercel AI Gateway.
Vercel AI Gateway supports TypeSafe Jev under model identifier typesafe-ai/jev through three distinct integration patterns: the official TypeSafe client adapter, a direct HTTP evaluation endpoint, and the Vercel AI SDK.
Routing Jev through Vercel provides centralized API key management via AI_GATEWAY_API_KEY, consolidated Vercel platform billing, and built-in observability without requiring separate credentials from TypeSafe.
The Three Documented Access Patterns
Depending on your architecture and existing dependencies, Vercel provides three supported integration pathways for Jev:
@typesafe-ai/sdk package, pointing its base URL to https://ai-gateway.vercel.sh/typesafe while authenticating with your Vercel gateway key. This route preserves TypeSafe's native question vocabulary (including noul).https://ai-gateway.vercel.sh/v1/evaluate with model string typesafe-ai/jev, accepting a keyed questions object using Vercel's native types (boolean, choice, score).ai): Uses the experimental_evaluate method exported directly by the core ai package, specifying typesafe-ai/jev and reading evaluated outputs directly from result.answers.Which Route Should You Use?
| Integration Pattern | Package / Endpoint | Best Suited For | Question Vocabulary |
|---|---|---|---|
| TypeSafe SDK Client | @typesafe-ai/sdk baseURL: .../typesafe | Teams with existing TypeSafe code needing fully-typed response schemas with Vercel observability. Reads answers from result.answers. | noul, choice, score (with criteria) |
| HTTP Evaluation API | POST /v1/evaluate | Microservices, edge runtimes, curl scripts, Python backends, or languages without dedicated TypeScript SDKs. | boolean, choice, score (with instructions) |
| Vercel AI SDK | import { experimental_evaluate } from "ai" | Next.js applications already using Vercel AI SDK for LLMs, wanting unified telemetry, middleware, and tracing. Reads from result.answers. | boolean, choice, score (with instructions) |
/typesafe) and Vercel-native evaluation route (/v1/evaluate and AI SDK experimental_evaluate) expose slightly different question vocabulary even though both route to Jev. Specifically, the TypeSafe client pathway uses TypeSafe's native primitives (including noul for binary propositions with continuous probability), whereas the native Vercel evaluation API and AI SDK expose boolean, choice, and score types with instructions.Pattern 1: TypeSafe SDK with Vercel Base URL
If you already use @typesafe-ai/sdk, you can redirect all inference traffic through Vercel AI Gateway by setting baseURL: "https://ai-gateway.vercel.sh/typesafe" and authenticating with your Vercel gateway key:
Pattern 2: Vercel AI Gateway HTTP Evaluation API
For zero-dependency REST integrations, Vercel AI Gateway exposes a dedicated evaluation endpoint at POST https://ai-gateway.vercel.sh/v1/evaluate:
Pattern 3: Vercel AI SDK (experimental_evaluate)
When developing in Next.js or Node.js environments with the Vercel AI SDK, invoke Jev using the experimental_evaluate export from ai:
Authentication & Environment Setup
All requests through Vercel AI Gateway authenticate using the standard gateway environment variable:
AI_GATEWAY_API_KEY in your project settings or .env.local. (Do not confuse this with unverified alternative key names.)typesafe-ai/jev.Billing & Pricing
Vercel currently lists Jev as Free under a promotion ending September 25, 2026. Outside promotional pricing, consult Vercel's live Vercel Jev model card ↗ and TypeSafe's direct pricing.
Refer to the live Vercel Jev model card ↗ for current post-promotion billing details, or check our Jev Pricing Reference.