decision.host
首页 / 模型 / GPT-6 Luna(Decisions API)

GPT-6 Luna(Decisions API)

OpenAI ChoiceNoulScore图像 curatedopenroutersom

OpenAI 的 Decisions API 后端模型,支持图像,最多 200 个问题/请求,三原语叫 predicate / choice / score。$0.10/百万输入 token,输出免费。

该模型目前没有出现在 S1MB 或 Decision Index 的公开评测结果中。

模型信息

厂商
OpenAI
类别
托管 API
参数规模
未公开
权重
闭源 / 未公开
许可证
闭源 需自行核对
输入模态
文本 图像
决策原语
ChoiceNoulScore
上下文
1,050,000 token
输入价格
$0.1/M tok
可微调
不支持
微调方法
无决策微调;OpenAI 微调平台本身正在收缩(仅存量用户可继续)
OpenRouter 模型 ID
openai/gpt-6-luna-decisions
OpenRouter 计费
输入 $0.1/M tok · 输出 免费
上架状态
Early access

数据来源与链接

本站聚合自: curated、openrouter、som。 分数与链接均指向原始出处。

来自 systemonemodels.org 的详细介绍

What the Decisions API is

The Decisions API is OpenAI’s hosted API for typed decisions. It does the job of a System One model, though OpenAI does not use that term. OpenAI announced it at DevDay on 29 September 2026. You define questions, each with a fixed list of possible answers, and send context as text or images. The API returns an answer from your list. OpenAI says it runs on GPT-6 Luna, the cheapest model in the GPT-6 family.

What it returns

OpenAI’s posts say only that you get an answer back, “a selection” in its X thread. The New Stack reports predefined answers with confidence scores. OpenAI has not published the response format, whether the scores are probabilities, whether they are calibrated, or whether the API supports Score or Noul questions. Only a Choice is confirmed, so this page lists only that.

What it is good at

OpenAI names three jobs: classify content, route requests, and choose an agent’s next action. Its X thread gives a support request and the teams it could go to as the example. Those map to support inbox triage, intent and model routing and agent routing and skill selection.

How it compares with Jev

Both are hosted APIs that pick from answers you define. The Decisions API accepts images as well as text, which no other model on this site claims. Jev reads text, publishes a price and a request format, and returns calibrated probabilities. Every, which had preview access, ran early tests. On a text replay of computer tasks, the Decisions API picked the right control in 76 of 78 steps against 73 for Jev. On a thread-classification test the two tied on accuracy and Jev was faster. Every says the Decisions API beat Jev on a few early tests but trailed on its broader evals. These are the testers’ own results. Two questions stay open until OpenAI publishes a reference. Does it return a probability for every option, as Jev does? And does it accept the /v1/systemone request shape that Jev and other models share?

What is not known yet

As of 30 September 2026, OpenAI has published no docs page, endpoint, price, limits, SDK support, benchmark or statement on calibration. The API does not appear in OpenAI’s docs changelog, in the latest Python and Node SDK releases, on OpenRouter or in the Hugging Face Decision Index. The New Stack also lists whether developers can tune it on their own data as unclear. An OpenAI spokesperson told The New Stack that OpenAI plans to share more at broad rollout.

Access

Preview access is limited to selected API customers. OpenAI says broad release is planned in the coming days, while Every expects a launch in a few weeks. This page will be updated when OpenAI publishes docs and pricing.

Specifications

Question types Choice Max Choice optionsNot documented Score levelsNot documented Questions per callNot documented Total contextNot documented State budgetNot documented Rate limitNot documented SDKs OpenAI has published no limits for the Decisions API. The New Stack lists the number of answers per request as unclear. GPT-6 Luna itself has a 1,050,000-token context window, but OpenAI has not said the Decisions API offers the same window. Checked on 2026-09-30.

Versions

Limited preview, 29 Sep 2026, OpenAI names no version or model id. It describes the API as built on GPT-6 Luna, and The Decoder describes a version of Luna made for it. Preview access is limited to selected API customers. Release notes

Use cases

What people use OpenAI Decisions API for, one page per pattern. Workflow controlStarter

Support inbox triage with System One models

Send a support ticket to Jev once with every question attached. Category comes back as a selected label, severity and frustration as numbers on scales you wrote, refund intent as a probability. Your code reads those values and decides what happens to the ticket. Choice Score Noul Workflow controlIntermediate

Intent and model routing with System One models

One Jev call reads an incoming request and returns its intent as a label plus a difficulty rating on a scale you wrote. Your router reads both numbers and picks the handler: deterministic code, a cheap model, an expensive one, or a human queue. Choice Score Real-time and agentsIntermediate

Agent routing and skill selection with System One models

An agent choosing from a long skill roster reads one truncated line per entry and often loads the wrong thing. Jev ranks every entry in one request and separately answers whether any skill applies at all, so the agent gets a short hint instead of a guess. Choice Noul VendorOpenAI TypeCommercial, hosted API StatusEarly access Announced29 Sep 2026 AccessOpened 29 Sep 2026 Input priceNot published Output priceNot published LatencyNot published ContextNot published Rate limitNot published API docsdevelopers.openai.com