Now available: GPT-6 Luna Decisions

Try the model

Decision models · Reviewed October 7, 2026

OpenAI Decisions API vs Jev

Give software a bounded decision it can act on.

OpenAI released Decisions API in beta on October 6. GPT-6 Luna Decisions is now available here through OpenRouter, using the same state and typed questions as Jev. The native OpenAI protocol differs; this comparison explains the integration actually offered on this platform.

This is an independent platform with no affiliation to OpenAI or TypeSafe. GPT-6 Luna Decisions is served through OpenRouter using this platform’s account, API key and credits.

Verified integration and open questions

Price, latency, and calibration need different evidence

Live requests verified text, JSON objects, arrays and image inputs through OpenRouter. These are contract checks, not a matched accuracy benchmark or a production latency SLA.

Provider input price

Jev

$0.042 / 1M

OpenAI Decisions API

$0.10 / 1M

OpenRouter lists Jev at $0.042 and GPT-6 Luna Decisions at $0.10 per million input tokens. This platform charges 600 and 1,500 credits respectively, with a one-credit minimum and rounding per successful request. Output tokens add no charge.

OpenRouter · GPT-6 Luna Decisions

Latency evidence

Jev

Test your cases

OpenAI Decisions API

Measure your workload

The three text contract probes took 304–401 ms end to end from the verification environment. They are too small a sample for p50/p95, an SLA or a fair speed comparison with Jev.

OpenRouter · GPT-6 Luna Decisions

Probability calibration

Jev

RLCD

OpenAI Decisions API

Unconfirmed

TypeSafe describes RLCD training. The verified API responses do not establish calibration or comparative accuracy for GPT-6 Luna Decisions. Measure both on labeled data before selecting thresholds.

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.

Try GPT-6 Luna Decisions

Image requests are verified through OpenRouter. This platform accepts up to 4 PNG, JPEG or WebP images under its upload limits. Use the model page for a preselected image-capable playground.

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 · OpenRouter integration

A shared Jev contract on this platform

Use openai/gpt-6-luna-decisions with state and a questions object at this platform’s /v1/systemone. OpenRouter converts between its Jev-style contract and OpenAI’s native Decisions API.

  • Read Choice, Score and Noul answers in data.result.answers; input usage determines credit charges.
  • OpenAI’s native API uses input, question/answer arrays and predicate/probability fields. Its payload is not accepted as a Jev request here.
  • This platform allows 8 questions and 32 KiB text plus questions, even though the upstream listing advertises a larger context and more questions.

Side-by-side comparison

Native OpenAI documentation and the OpenRouter contract used here

Core task
JevTyped decisions for software
OpenAI Decisions APITyped classification, routing and scoring
Underlying model
JevJev / System One
OpenAI Decisions APIGPT-6 Luna Decisions
Input
JevText and structured text state
OpenAI Decisions APIText, JSON or images through OpenRouter
Question types
JevNoul, Choice, Score
OpenAI Decisions APIChoice, Score and Noul on this platform
Output
JevTyped answers and probabilities; Choice/Score confidence
OpenAI Decisions APIAnswers keyed by question ID through OpenRouter
Calibration
JevRLCD described by TypeSafe; validate on your data
OpenAI Decisions APICalibration on your workload remains unmeasured
Endpoint / schema
JevPublic HTTP reference for /v1/systemone
OpenAI Decisions APIThis platform: /v1/systemone; OpenAI native: /v1/decisions
Billing
JevVendor input price published; site credits are separate
OpenAI Decisions APIOpenRouter: $0.10/M input, output free; platform: 1,500 credits/M
Latency
JevWorkload-specific measurement needed
OpenAI Decisions APINo matched latency comparison or SLA
Available on this site
JevYes, with this service’s account and credits
OpenAI Decisions APIAvailable through OpenRouter with this platform’s credits

Sources and scope · October 7, 2026

OpenAI’s official changelog and Decisions reference establish the beta launch and native schema. OpenRouter’s model and endpoint listings establish this integration’s model ID, context and prices. Live synthetic probes verify all three answer types, text/object/array state, 8 questions, option boundaries, a long-state marker and contrasting images. A simulated refusal response verifies refund handling; the live refusal probe returned a normal answer. No matched accuracy or calibration benchmark was run.

Try GPT-6 Luna Decisions