DecisionsApi
Invite-only access: OpenAI Decisions APIExplore the playground

DecisionsApi · Decision API OpenAI

DecisionsApiDecision API for OpenAI workflows

Add an independent decision layer to applications that use OpenAI. Test how to classify requests, score urgency, and route the next step with structured answers your backend can use.

Try a decision in the playgroundExplore the decision API
Typed decision outputsMultiple questions per inputProbability signals

Decision workflow example

No credits used

Customer message

“I was charged twice this morning. Please refund the duplicate payment today.”

One message → three decision signals

Choice

Billing

Select the billing workflow

Yes / no

96%

Probability of an urgent request

Score

2.8 / 3

Urgency on a 0–3 scale

Static illustration of this platform's output format. These values are not a live response, an accuracy claim, or an OpenAI API response.

01 / Workbench

Decision workbench

Choose a task, edit the input, define typed questions, and preview the request before you connect the same workflow to your backend.

Unlimited free use in the online playground.

Workbench

What do you want to decide?

Choose a scenario to load editable input and rules. Loading an example uses no credits.

Examples load into the current draft only; no configurations or run history are saved.

State

Give the selected model the context shared by every question.

Text

All questions share this context and are answered independently.

Questions

Define up to eight typed questions for the same state.

3 / 8

3. Run decision

Run the decision request.

Result preview

Subject: Charged twice again!! Hi — this is the SECOND month in a row I've been billed twice for the Pro plan. I already emailed last month and nobody replied. I run my whole business on this. If it's not refunded today I'm cancelling and disputing the charge with my bank.

↓One input → multiple structured decisions

Click “Generate decisions” to see typed output with probabilities.

Results are returned in a structured format so you can connect them to your application logic.

02 / Connect the workflow

Make the next step an explicit decision.

Your backend can call a decision model before or after an OpenAI request. Supply the relevant context, inspect the result, and apply your own rules before taking action.

01

Provide the context

Send the incoming request, a generated draft, or the records needed to answer your decision questions.

state = ticket.text
02

Define bounded questions

Specify the routing labels, scoring levels, or yes-and-no criteria that your application understands.

questions = { intent, urgent }
03

Inspect structured answers

Read each typed answer alongside its probability signals and request details before using it in your workflow.

answer = result.answers.route
04

Apply application rules

Use the result to select a workflow, continue a model call, or request human review. Your application controls execution.

if result.urgent: escalate()

03 / Practical applications

Where a decision API fits in an OpenAI app

Start with one repeated judgment in your product. Test representative and ambiguous inputs before connecting the result to an automated action.

01

Classify and route requests

Assign billing, technical, account, or other labels before choosing a support workflow or preparing context for a generated reply.

02

Choose the next agent step

Decide whether a request needs a record lookup, an OpenAI model call, another tool, or human review using options you define.

03

Score drafts for review

Evaluate a draft against explicit relevance or completeness criteria, then use the score to send selected responses for further review.

04 / Work with typed outputs

Three decision formats your code can use

Express classification, scoring, and focused checks as bounded questions. The returned signal gives your application a defined input for its next step.

Choice for classification

Choose from labels you provide, such as billing, support, or review. Map each answer to an existing application workflow.

Score for prioritization

Define ordered levels for urgency, relevance, or completeness. Evaluate the same criteria across examples from your OpenAI application.

Noul for yes-or-no checks

Ask a focused question and use its returned probability with a threshold you have evaluated on your own cases.

Integrate from your backend

Call the decision layer from your application

The example below calls this platform's /v1/systemone endpoint with Jev, using a platform API key. Keep it as a separate server-side request in your workflow; this is not an OpenAI endpoint or an OpenAI SDK example.

Read the platform API docs
Server-side REST requests
Structured decision responses
Platform API keys

This platform's decision API

Server-side JavaScript · Jev request example

POST /v1/systemone
const response = await fetch(
  "https://decisionapi.net/v1/systemone",
  {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${DECISIONS_API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      model: "typesafe/jev-1.13",
      state: ticket,
      questions: { route: { type: "choice", criteria } }
    })
  }
);

05 / Understand the service

Start building with Decisions API

Testing credits included

New users receive credits for testing, so you can create an account, load an example, review the budget, and run your first questions.

One wallet for every live call

Use the same credit balance across the playground, API, and evaluation workflows. Credits from purchased packs do not expire.

Usage you can inspect

Review request history and credit activity, and use request identifiers to connect API calls with their usage records.

Pricing

Decisions API turns unstructured state into typed decisions with probabilities for classification, routing, scoring, and safety checks. Choose monthly, yearly, or one-time access for your usage.

One-time plans do not auto-renew or require a long-term subscription; the $10, $100, and $1,000 tiers include credits that remain available after purchase.

Important: Decisions API is currently in limited testing

Decisions API is not fully open yet and is currently available only for a small-scale test. Access will be enabled in payment order, and we’ll notify you by email. In the meantime, you can use Jev AI and other Decision APIs.

Starter

$10

Validate one real workflow, from the playground to your first API call

  • 100,000 credits, no expiry
  • 1 workspace
  • 3 concurrent requests
  • Standard speed
  • Choice, score, and noul questions
  • Typed decision output
  • Probability and confidence results
  • Online playground
  • API key management
  • Email support
Recommended

Pro

$100

Connect classification, routing, and safety decisions to a production product

  • 1,000,000 credits, no expiry
  • Unlimited workspaces
  • 10 concurrent requests
  • Fast lane
  • Choice, score, and noul questions
  • Typed decision output
  • Parallel questions per request
  • API access
  • Usage and request history
  • Priority support

Enterprise

$1,000

For multiple workspaces, team collaboration, and custom production integrations, with 10% extra credits

  • 11,000,000 credits (10% extra included)
  • Everything in Pro
  • Unlimited concurrency
  • Dedicated fast lane
  • Team workspaces and collaboration
  • Custom integration support
  • Security and permission guidance
  • Dedicated support
  • Priority production processing
  • Product roadmap feedback

Compare before you ship

Choose models with evidence from your own cases

Published benchmarks are useful background, but production choices should also reflect answer quality, uncertainty, latency, and cost on inputs that resemble your workflow.

Decision qualityResponse speedCost per decision
Explore model comparisons

Jev

Typed choices, scores, and yes–no decisions

01

Laya

English and multilingual decision workflows

02

Kev, Solar, and Span

Additional models for comparison and evaluation

03

Recent blog posts

What we are learning

Product notes, technical details, and practical ways to use Jev.

View all posts
Decisions API vs Jev: Differences & Integration Guide

AI APIs

Decisions API vs Jev: Differences & Integration Guide

Compare Decisions API vs Jev: platform and model differences, typed outputs, API integration, cost evaluation, and a practical checklist for choosing your stack.

Oct 3, 2026 · 11 min read

OpenAI Decisions API Luna Model: A Practical Guide

AI Models

OpenAI Decisions API Luna Model: A Practical Guide

Understand the OpenAI Decisions API Luna model, preview status, bounded decisions, routing contracts, evaluation, and a practical path to production.

Oct 3, 2026 · 12 min read

Decision API OpenAI: Integration Guide and Practical Examples

Developer Guide

Decision API OpenAI: Integration Guide and Practical Examples

Build a decision API OpenAI workflow with typed outputs, a REST example, evaluation metrics, and production controls. Understand the different API contracts.

Oct 3, 2026 · 11 min read

Decisions API Documentation: Request Format, Question Types, and a Working Example

AI APIs

Decisions API Documentation: Request Format, Question Types, and a Working Example

A practical Decisions API documentation guide with the REST request format, Choice, Score, and Noul questions, a support-routing example, and production safety patterns.

Oct 1, 2026 · 11 min read

Decision API OpenAI: common questions

Understand how an independent decision layer can fit into your OpenAI application workflow.