Jev vs Perplexity Decisions
Perplexity shipped a Decisions API in September 2026: model pplx-decider-v1-27b handling noul/choice/score questions, 1–128 questions per call, images via base64, $0.04/M input (output free). TypeSafe's Jev launched the same month. Both are GA decision APIs; Perplexity has vision and slightly lower per-token cost, Jev has text-only simplicity and documented builds.
Updated 2 Oct 2026 · by Made with Jev
In short
- Jev: text-only, $0.042/M input (output free), GA via TypeSafe API, closed weights, madewithjev proof builds.
- Perplexity Decisions: multimodal (images via base64), $0.04/M input (output free), 1–128 questions, input under 262k tokens.
- Both: GA, noul/choice/score question types, per-option probabilities and confidence, batch multiple questions per call.
- Difference: ~5% per-token cost, vision support, proof builds. Same category validation: typed decisions beat generative prose for classify/route/act.
What Perplexity announced
From the Perplexity Decisions quickstart:
- Model:
pplx-decider-v1-27b - Endpoint:
POST https://api.perplexity.ai/v1/decisions - Question types: noul, choice, score
- Input: text and images (images via base64 data URLs in state)
- Batch: 1–128 questions per call
- Context: input under 262,144 tokens
- Pricing: $0.04 per million input tokens, output free
Source: Perplexity Decisions quickstart
What Jev is
TypeSafe's Jev is a decision model (System One), not a chat model that happens to pick a label. Launched September 15, 2026.
- Question types: Choice, Score, Noul (mixable in one call)
- Returns: per-option probabilities and confidence
- Input: text only (string, JSON object, or array of strings)
- API: documented
POST /v1/systemonewith Python and JavaScript SDKs - Pricing: $0.042 per million input tokens, output free
- Batch: ~60 questions cost about the same as one
- Limits: 64k tokens per request; 32k for state plus longest question
Source: TypeSafe models
Side by side
Facts only. Where either product has not published a detail, that is what the table says.
| TypeSafe Jev | Perplexity Decisions | |
|---|---|---|
| Announced | Sep 15, 2026 | Sep 2026 |
| Availability | Generally available | Generally available |
| Model | Purpose-built System One | pplx-decider-v1-27b |
| Public contract | Documented POST /v1/systemone + SDKs | Documented POST /v1/decisions |
| Question types | Choice, Score, Noul | noul, choice, score |
| Probabilities / confidence | Per-option probs + confidence | Per-option probs + confidence |
| Input modalities | Text only | Text + images (base64) |
| Max questions per call | ~60 cost about the same as one | 1–128 |
| Context limit | 64k tokens per request | Input under 262,144 tokens |
| Price | $0.042 / M input; output free | $0.04 / M input; output free |
| Open weights | No (closed) | Not published (as of early Oct 2026) |
| Self-hostable | No | Not published |
| Proof builds | madewithjev catalog | Vendor benchmarks only |
Price difference: Perplexity $0.04/M vs Jev $0.042/M input = $0.002/M tokens or ~5%. Marginal difference; both significantly cheaper than chat models for routing/classification.
Latency caveat: Neither vendor publishes P50/P99 latency as of early October 2026. Do not compare vendor slides to third-party measured figures without labeling methods.
What builders should do
- If you need vision (screenshots, UI state): Perplexity documents images via base64 data URLs. Jev is text-only; preprocess images with OCR or vision models if using Jev.
- If you want proof builds: Jev has madewithjev catalog with published cost/latency figures. Perplexity: vendor benchmarks only as of early October 2026.
- If you want lowest per-token cost: Perplexity $0.04/M, Jev $0.042/M — difference is ~5%. For text-only high-volume workflows, Perplexity has marginal edge.
- If you are already using Perplexity APIs: Adding Decisions to existing Perplexity billing is simpler than wiring a second vendor.
- If you need agent orchestration patterns: Jev has documented skill/MCP/orchestration rules for Claude Code, Cursor, Codex. Perplexity: check current docs for agent integration.
How to talk about timing
Jev mid-September, Perplexity Decisions September, Cloudflare Clef late September, OpenAI Decisions (DevDay) in the same window. Frame it as category validation: the industry agrees that constrained typed decisions at speed beat generative prose for classify/route/act workflows. No vendor has stated they copied another.
Builds that show the job
Routing, classification, and agent next action — with the cost and latency each builder published.
Duncan
@ephraimduncan
Built a model router with Jev by @typesafeai. Jev decides what model fits your request best and the request is sent to that model.
XRouting and model choice
A model router on Jev
Gregor Zunic
@gregpr07
Breaking: Browser Use + Jev = Ultrafast ⚡ Findings flights took 7s and cost only $0.0039 🤯 > new action space every step > DOM state space > small LLM fallback to type (this video is at 1x speed btw) Built a tiny open source browser agent. try it below ↓
tamara
@tamarajtran
found the perfect use case for @typesafeai Jev: instant compaction in 2026, why is compaction still a summarization prompt? Jev can make it instant by scoring every tool call and dropping what’s irrelevant
XContext and memory
PickInstant compaction for Claude
Hassan
@nutlope
I used Jev to classify 1,018 AI research papers. The result: $0.08 total cost and 256ms median end-to-end latency per paper. The pipeline was: 1. Summarize each paper with DeepSeek V4 Flash 2. Send the title + summary + 24 possible topics to Jev 3. Use Jev to classify each paper 4. Visualize everything on http://1kpapers.com The summaries cost $3.99 on @togethercompute. The classifications cost $0.08 on @typesafeai. So for just over $4 of inference, I ended up with a pretty useful way to explore the top AI research papers from the past year. I think this is where things are heading: different models for different parts of the workflow, instead of using one model for everything. I’m running evals on the Jev classifications before replacing the current ones, but the site is already live: http://1kpapers.com
More on Jev use cases.
Try it today
Next steps
- Perplexity Decisions alternatives — who should use Jev instead, and when Perplexity still wins
- How to use Jev — your first call, SDKs, and gateways
- Jev pricing — what a decision costs across real builds
- Open-source Jev — local models that answer typed questions
- Agent prompts — wire Jev into Claude Code, Cursor, Codex
Common questions
- What is Perplexity Decisions API?
- A decision API on model pplx-decider-v1-27b. Handles noul/choice/score question types, 1–128 questions per call, images via base64 data URLs, input under 262,144 tokens. Generally available with documented API and pricing ($0.04/M input, output free).
- How is Jev different from Perplexity Decisions?
- Jev is text-only, $0.042/M input (output free), closed weights, madewithjev proof builds, ~60 questions cost about the same as one. Perplexity Decisions is multimodal (images via base64), $0.04/M input, 1–128 questions, no published open weights as of early October 2026.
- Which is cheaper, Jev or Perplexity Decisions?
- Very close: Perplexity $0.04/M input, Jev $0.042/M input (both output free). Difference is $0.002/M tokens or ~5%. Both significantly cheaper than chat models for routing/classification.
- Does Perplexity Decisions support images?
- Yes. Perplexity Decisions accepts images via base64 data URLs in state, per their quickstart docs. Jev is text-only; preprocess images with OCR or vision models.
- Do both return probabilities and confidence?
- Yes. Both return per-option probabilities and confidence scores. Your code can act on confident answers automatically and escalate uncertain ones to a person or larger model.
- Which should I use for agent routing?
- If you need vision (screenshots, UI state): Perplexity. If text-only and want proof builds: Jev has madewithjev catalog. If want lowest per-token cost: Perplexity $0.04/M, Jev $0.042/M — marginal difference. Both are GA with documented APIs.
Made with Jev is independent and not affiliated with TypeSafe AI. Every figure on this page is the one its author published, linked to where it can be checked.