Decision models · Reviewed September 30, 2026

OpenAI Decisions API vs Jev

Give software a bounded decision it can act on.

A routing task needs a category or a next step. Jev has a documented decision API; coverage of OpenAI’s September 29 DevDay describes a new Decisions API in limited preview. This comparison separates published documentation from launch reporting.

This is an independent comparison. This website is not affiliated with OpenAI or TypeSafe. OpenAI Decisions API is not integrated into this playground or API.

Evidence and open questions

Price, latency, and calibration need different evidence

The OpenAI changelog and endpoint index checked on September 30 did not list a dedicated Decisions API reference. Reported demo numbers do not establish a production SLA or a head-to-head benchmark.

Official input price

Jev

$0.042 / 1M

OpenAI Decisions API

Unconfirmed

TypeSafe lists $42 per billion input tokens, equivalent to $0.042 per million. This is the vendor’s price; this independent service uses its own credit rates. OpenAI preview pricing was not verified.

TypeSafe pricing

Latency evidence

Jev

Test your cases

OpenAI Decisions API

~150 ms*

*Launch coverage reports an approximately 150 ms demonstration on a specialized GPT-6 Luna version. This is not an SLA. We have no matched workload, region, concurrency, or p95 comparison with Jev.

Launch report · secondary source

Probability calibration

Jev

RLCD

OpenAI Decisions API

Unconfirmed

TypeSafe describes training for calibrated decisions with RLCD. No Decisions API-specific calibration method was found in the checked OpenAI docs. That does not prove its probabilities are uncalibrated.

TypeSafe explanation of RLCD

A bounded decision

Which support branch should run next?

Define the available branches and the evidence that separates them. A decision model returns a signal your code can use. A chat model with structured outputs can also fit a schema, but a valid JSON shape alone does not establish decision quality or calibration.

Context
“I paid yesterday but still don’t have access.”
Question
What should happen next?
Possible answers
BILLING_SUPPORTTECH_SUPPORTREFUNDGENERAL_SUPPORT
Illustrative application branch
BILLING_SUPPORT → review payment and access
Illustrative application logic, not a live result or an OpenAI request schema. Your application uses the selected branch to review the relevant payment and access records.

Choose around your workload

What information does the next step need?

01

Route text, score quality, or check a claim.

Evaluate Jev today

Start with its published Noul, Choice, and Score contract. In the playground, test normal, ambiguous, and incomplete inputs against your own expected answers.

02

Classify a product photo or review a UI screenshot.

Assess the reported visual path

Launch coverage describes text and image context for OpenAI. Once official access and image limits are clear, test product categories, generated-image pass/retry decisions, or document routing with visual evidence. These are potential uses, not features offered here.

03

Use a probability to trigger an action.

Measure both on the same cases

Compare error rates, probability calibration, cost, and p50/p95 latency with representative labeled data. Define a review threshold and a fallback in application code. A confident score does not guarantee a correct decision.

From evaluation to integration

Keep the model contract separate from application policy

Jev · TypeSafe System One model

A published decision contract

TypeSafe documents POST https://api.typesafe.ai/v1/systemone. Requests carry state, model, and typed questions; responses return answers keyed by question ID.

  • Noul returns a yes probability. Choice and Score include probability distributions and derived confidence.
  • State accepts text, objects, and arrays. This comparison covers the documented text workflow, not future multimodal models.
  • The playground on this site uses its own account, API key, endpoint, and credit balance. See our API docs for this service.

OpenAI · reported preview

Confirm the public contract first

Pasquale Pillitteri’s launch report describes a GPT-6 Luna specialization that chooses from finite answers using text or image context. These details remain launch reporting in this comparison.

  • Get confirmed access and an official request and response schema before implementing a client.
  • Do not assume a /v1/decisions path, Jev-compatible payload, model ID, or SDK method.
  • Verify official pricing and probability semantics. A broader rollout date is not established by the docs checked here.

Side-by-side comparison

Documented behavior and reported preview details

Core task
JevTyped decisions for software
OpenAI Decisions APIFinite-answer decisions · reported
Underlying model
JevJev / System One
OpenAI Decisions APISpecialized GPT-6 Luna · reported
Input
JevText and structured text state
OpenAI Decisions APIText and images · reported; limits unverified
Question types
JevNoul, Choice, Score
OpenAI Decisions APIPredefined answers · reported; full type system unverified
Output
JevTyped answers and probabilities; Choice/Score confidence
OpenAI Decisions APISelected answer and a score · reported; exact fields unverified
Calibration
JevRLCD described by TypeSafe; validate on your data
OpenAI Decisions APINo method verified in checked official docs
Endpoint / schema
JevPublic HTTP reference for /v1/systemone
OpenAI Decisions APINo dedicated reference found in checked official index
Billing
JevVendor input price published; site credits are separate
OpenAI Decisions APIOfficial price unverified; do not infer from standard Luna
Latency
JevWorkload-specific measurement needed
OpenAI Decisions API~150 ms reported demo; no matched comparison or SLA
Available on this site
JevYes, with this service’s account and credits
OpenAI Decisions APINo integration at this time

Sources and scope · September 30, 2026

OpenAI launch details above are attributed to Pasquale Pillitteri’s September 29 report. We checked OpenAI’s public changelog and endpoint index; neither provided a dedicated Decisions API entry at review time. Jev’s contract, confidence behavior, and price come from TypeSafe’s own material. No side-by-side test was run. Check each provider’s latest documentation for current availability and prices.

Try Jev in the playground