Published
Updated
OpenRouter, Cloudflare, and Netlify start serving Jev
This topic was created 12 days ago, and the information it contains may have evolved or changed since then.
Opened October 19, 2026, Cloudflare lists typesafe/jev-1.14.0 at $0.042 per million input tokens, output free, and a 32,000-token window. OpenRouter's typesafe/jev-1.14 listing stays 262K. GET /api/v1/models did not list that OpenRouter id. This desk did not call either host.
On September 18, OpenRouter announced beta support for Jev. The listing adopts TypeSafe’s stated pricing and latency: $0.042 per million input tokens, free output, response times between 70 and 500 ms, and claimed speedups over comparable language model workflows. The endpoint differs from standard chat completions, routing instead through POST https://openrouter.ai/api/alpha/decisions under the model identifier ~typesafe/jev-latest, which resolves to Jev 1.13. OpenRouter also offered $20 in platform credits to ten projects tagging @jjacky.
A day earlier, Cloudflare developer and AI lead Rita Kozlov shared that Jev was available on Cloudflare AI Gateway following public coordination with TypeSafe. Cloudflare serves typesafe/jev through Workers AI (env.AI.run) with a listed 32,000-token context window, while billing rates are managed through the Cloudflare dashboard.
Netlify announced similar availability in a changelog update on September 17. Developers can access Jev through Netlify AI Gateway by installing @typesafe-ai/sdk, initializing a TypeSafeClient within Netlify Functions, and billing usage directly to platform credits. The accompanying sample demonstrates routing incoming contact submissions between sales, support, and spam.
With Vercel having added typesafe-ai/jev on September 16, developers can now access the model through Vercel, Cloudflare, Netlify, or OpenRouter without waiting for direct access from TypeSafe.
Provider listings reflect slight differences in categorization and limits. OpenRouter labels its endpoint as alpha and the model as beta. Cloudflare lists Jev under text generation. While Netlify and OpenRouter cite a 32,000-token context window, TypeSafe’s documentation specifies 64,000 tokens for the full request and 32,000 tokens for state combined with the longest question.
On September 24 at 16:16 UTC, Diogo Almeida posted a screenshot of OpenRouter’s context-length chart. The filter is prompts and completions of 1K to 10K tokens, and the count is absolute requests. The ranking under the chart lists Jev 1.13 by typesafe first, at 242 million requests and 15.1%. DeepSeek V4 Flash 0731 is second at 160 million and 9.9%. DeepSeek V4 Flash 0423 is third at 120 million and 7.5%. Gemini 2.5 Flash Lite is 69.5 million and 4.3%. GPT-5.6 Luna is 67.3 million and 4.2%. The date labels on the same image run from Mar 30 to Sep 14. The caption says Jev is the top model in that band. It does not print a separate total for the week of the September 15 launch. Fraser Price replied that the chart is request count, which matches the subtitle “Requests by prompt & completion length.” Alex Atallah, OpenRouter’s CEO, replied with a heart. We did not pull a rankings export, and we did not call the Decisions API.
On September 25 at 22:21 UTC, OpenRouter posted typesafe/jev-router. The router uses Jev to pick a model and a reasoning effort before each turn. The thread says Jev reads the conversation text and scores difficulty, precision, whether a bigger model or more effort would help, whether a cheaper model is enough, and whether the task changed. Attachments are not sent to Jev. The call is under zero data retention. The router keeps a working model for the rest of the session and can change effort without switching. It switches when the expected gain is larger than the cost, including the cached chat it would lose. If the Jev call times out or the output is invalid, the request fails instead of falling back to another router.
The same thread says that on four agent benchmarks Jev Router solved 237 of 423 tasks and Auto Router solved 130 of 423. The post calls that 82% more tasks. A later post says that on five agent benchmarks Jev Router had a faster median time to first token than every other router tested. It does not print those times. The model id for chat completions is typesafe/jev-router. The model page we opened documents that chat call. It does not reprint 237 or 130. TypeSafe quoted the announcement at 22:29 UTC.
On September 26 Theo posted that he spent $1,000 benchmarking Jev Router. He wrote that DeepSWE performance was roughly the same as GPT-6 Astra on low, that it cost slightly more, and that it took almost 5 times longer. The post includes a chart. We did not read a task-level table off that image, and we did not call the router.
On September 28 Christoph Görn logged sixteen of his own prompts through typesafe/jev-router on OpenRouter. The write-up is on görn.name. The answered_by field names openai/gpt-6-luna five times, deepseek/deepseek-v4.1-flash three times, and moonshotai/kimi-k3 once. Seven of the sixteen calls errored, which he reads as replies that did not contain a JSON object. Nine successful calls averaged 2.99 seconds, from 1.26 to 4.41. He had set a 3 second timeout on each socket operation, not on the whole request. Sizing cost about $0.0032. The outcomes he counted: tiny 3, everyday 1, large 1, self 4, error 7. He writes that he expected TypeSafe’s Jev and that the log shows general-purpose models instead. We did not pull his log file. The same post’s local arm, Jared Palmer’s Kev-4B, is in the Kev story.
The model page opened October 8, and Arena’s October 7 session count, are on the Jev Router page.
OpenRouter posted at 00:16 UTC on October 15 that Jev 1.14 is now on OpenRouter. Opened later that UTC day, typesafe/jev-1.14 lists $0.042 per million input tokens, output free, and a 262K context. The TypeSafe row on that page prints P50 0.15 s and uptime 100.00%. The latest alias page already linked Jev 1.14. GET https://openrouter.ai/api/v1/models did not list typesafe/jev-1.14. GET of that id returned HTTP 404. Reopened at 11:04 UTC, the HTML page still returned HTTP 200 and GET of that id still returned HTTP 404. This desk did not call OpenRouter. TypeSafe’s own jev-latest, Date header 11:04 UTC, still returned jev-1.13.0. The desk numbers sit on jev-1.14.0.
Taka Sasaki posted at 04:26 UTC on October 19 that Jev 1.14 is on Cloudflare AI. Opened that UTC morning, typesafe/jev-1.14.0 returned HTTP 200. Context window 32,000 tokens. Input $0.042 per million tokens, cached input $0.00, output $0.00. The page lists Noul, Choice, Score, and Box. Image inputs and Box questions are marked beta. A sample noul on a black-rectangle PNG prints 0.95. Cloudflare’s older typesafe/jev card stays 32,000 tokens. OpenRouter’s typesafe/jev-1.14 listing stays 262K. We did not call Workers AI.
This site's reading
Editorial notes evaluating claims against primary sources, contextualizing findings alongside related implementations, and defining technical terms.
Verify
OpenRouter's thread, TypeSafe's repost, and the public model listing confirm that Jev Latest is in beta on the platform, priced at $0.042 per million input tokens with free output, accessible via POST https://openrouter.ai/api/alpha/decisions as ~typesafe/jev-latest.
Cloudflare's listing appears on Workers AI docs as typesafe/jev, specifying a 32,000-token context window with account dashboard pricing. Opened October 19, 2026, developers.cloudflare.com/ai/models/typesafe/jev-1.14.0/ returned HTTP 200. Model id typesafe/jev-1.14.0. Context 32,000 tokens. Input $0.042 per million tokens, output $0.00. Image inputs and Box questions are beta. We did not call Workers AI. Netlify's changelog corresponds with company updates: TypeSafeClient runs inside Functions and bills against Netlify credits. We did not call these endpoints directly.
Almeida's September 24 screenshot, 16:16 UTC, is OpenRouter's context-length chart for requests whose prompt and completion fall in the 1K to 10K token band, counted in absolute requests. The list under the chart puts Jev 1.13 by typesafe first, at 242 million requests and 15.1%.
DeepSeek V4 Flash 0731 is 160 million and 9.9%. DeepSeek V4 Flash 0423 is 120 million and 7.5%. Gemini 2.5 Flash Lite is 69.5 million and 4.3%. GPT-5.6 Luna is 67.3 million and 4.2%.
The chart's date labels run from Mar 30 to Sep 14. The post does not print a separate total for the week of the September 15 launch. We did not pull a rankings export. On September 25 at 22:21 UTC OpenRouter posted typesafe/jev-router.
The thread says four agent benchmarks scored 237 of 423 for Jev Router and 130 of 423 for Auto Router, which the post calls 82% more tasks. A later post says five agent benchmarks gave Jev Router a faster median time to first token than every other router tested, and it does not print those times.
The model page we opened documents a chat-completions call for typesafe/jev-router and does not reprint 237 or 130. Theo's September 26 post says a $1,000 DeepSWE run was roughly even with GPT-6 Astra on low, slightly more expensive, and almost 5 times longer. We did not transcribe a task table from his chart.
We did not call the router. Christoph Görn's September 28 log of typesafe/jev-router, first 16 prompts, records answered_by as openai/gpt-6-luna five times, deepseek/deepseek-v4.1-flash three times, and moonshotai/kimi-k3 once. Seven of the 16 errored.
Nine successful calls averaged 2.99 s, from 1.26 s to 4.41 s. Sizing cost about $0.0032. The routed counts are tiny 3, everyday 1, large 1, self 4, error 7.
Compare
Vercel added typesafe-ai/jev a day earlier, covered in our waitlist article. Venice listed a beta Decisions API the night of September 18, with a no-retention claim and a /systemone alias, covered in a later story. Five hosting gateways and TypeSafe's direct API now offer access to the same model.
The performance metrics cited across partner documentation (70 to 500 ms, and 190x to 440x improvements) originate from TypeSafe's internal benchmarks.
OpenRouter and Netlify report a flat 32,000-token window, whereas TypeSafe and Venice specify 64,000 tokens for the total request and 32,000 tokens for the state plus the longest question. Cloudflare catalogs the model under Text Generation despite the payload consisting of state and structured questions.
Terms
- Decisions API
- OpenRouter's dedicated endpoint (POST /api/alpha/decisions) accepting state and typed questions rather than conversational message arrays.
- AI Gateway
- A cloud provider's managed proxy for AI APIs handling credentials, billing, and logs, such as those provided by Vercel, Cloudflare, and Netlify.
- jev-latest
- TypeSafe's alias for the current stable model release, currently routing to jev-1.13.0.
- Workers AI
- Cloudflare's serverless inference runtime, executing queries via env.AI.run('typesafe/jev', { state, questions }).
- Jev Router
- OpenRouter's typesafe/jev-router, posted September 25. The announcement says Jev scores the conversation, and the router picks a model and an effort. The thread's four-benchmark count is 237 of 423 against Auto Router's 130 of 423. Görn's September 28 log of the same model id names gpt-6-luna, deepseek-v4.1-flash, and kimi-k3 as the models that answered.
Sources
- OpenRouter announcement that Jev is in beta
- TypeSafe quoting the OpenRouter listing
- OpenRouter model page for Jev Latest
- Rita Kozlov, Jev live on Cloudflare AI Gateway
- TypeSafe quoting the Cloudflare listing
- Cloudflare Workers AI page for typesafe/jev
- Netlify on typed answers you can branch on
- Netlify changelog, Jev on AI Gateway
- TypeSafe models page (Jev 1.13 limits)
- Diogo Almeida, OpenRouter 1K to 10K chart
- Fraser Price, on request count
- Alex Atallah, reply
- OpenRouter, introducing typesafe/jev-router
- OpenRouter, 237 of 423 against Auto Router's 130
- OpenRouter, Jev Router model page
- TypeSafe, quoting the Jev Router post
- Theo, DeepSWE timing on Jev Router
- Christoph Görn, who answered jev-router
- Görn, router log
- Taka Sasaki, Jev 1.14 on Cloudflare AI
- Cloudflare Workers AI, typesafe/jev-1.14.0