GPT-6.1 Sol
以 OpenAI 3 折价格使用 GPT-6.1 Sol:输入 $0.60/1M tokens,输出 $3.00/1M tokens。对比 GPT-6 Sol 与 Astra,并提供 curl、Python 和 Codex 配置指南。
A codebase you don't know is a risk, not a hurdle. The plan should burn down that risk in order: understand, run, trace, spike, then make the change small enough that "production-ready" is a property you can demonstrate, not a hope.
Here are the first five steps, with the evidence you collect at each.
Step 1 — Get it building and the baseline green (half day)
Read the README, the manifest(s), the CI config, and any architecture docs. Boot the app locally, run the full test suite, run the linter/typechecker.
Evidence: The exact commands that reproduce a clean build and a passing test suite from a fresh checkout (recorded output, not memory of it). A one-page map you wrote yourself: where the entry points are, the layers, the build/test toolchain, and the main risks to your feature (e.g. "this touches cron jobs and payments").
Step 2 — Trace the smallest end-to-end slice that resembles your feature (half day)
Don't start with your feature. Pick a neighboring one that already works and follow it from entry to persistence. Note the conventions along the way: how errors surface, how config is injected, how logging is done, how tests are written.
Evidence: An annotated trace — file → function → what it does — for that slice. A written list of "conventions I must follow" (not intuitions; things you observed in real code). A named shortlist of the 3–5 files you will actually touch. If you can't produce this trace, you're not ready to write code.
Step 3 — Spike the core path (day 2)
Build the ugly version: hardcoded values, no error handling, no tests. The purpose is to confirm the path you traced in step 2 is real and to surface what you didn't know you didn't know.
Evidence: A working spike demonstrating the feature's central data path, alongside a list of every assumption the spike broke and what you corrected. That correction list is the most valuable document in this whole plan.
Step 4 — Write the contract before the code (half of day 2 / day 3)
Once the spike proves the path, pin down what production needs: the inputs/outputs, the error cases, where it sits in the conventions from step 2. Then write the tests — they'll be red, but they're the specification.
Evidence: A one-to-two-page design doc, an agreed interface/API shape (with the team if there is one), and a red test suite that encodes intended behavior. If you can't write the contract without consulting the code, you haven't finished step 2.
Step 5 — Implement in small, verified increments (days 3–4)
Replace the spike with the real thing in small commits, each one keeping the suite green, leaning on the existing patterns. Run lint/tests/typecheck per commit — CI, not just locally — and exercise the actual path against a real instance (staging or a local environment that isn't stubbed).
Evidence: A branch with progressive commits, each green in CI; coverage on the new code; something that proves it works against reality (a test result, a log trace, a screenshot); and a review by at least one person who knows the codebase. The review counts as evidence — an unfamiliar codebase has tribal knowledge you cannot extract from the files alone.
Steps 6+ would be the things that actually make it "shipped": a migration plan and its rollback, feature flagging, observability, the release and post-release verification. But the first five get you to a reviewed, green, working slice in staging — which is the point at which you can say "this will work in production" with evidence behind it, instead of a guess.
运行会以此提示词打开 AI Chat,需要登录并有积分。
模型详情
在 Playground、API 请求和内部工作流中使用相同的模型 key。
- 模型 ID
- gpt-6.1-sol
- 供应商
- OpenAI
- 协议
- OpenAI Chat Completions
- 上下文窗口
- 1,050,000 Token
- 最大输出
- 128,000 Token
GPT-6.1 Sol 是什么
GPT-6.1 Sol 代码示例
用 3 步试用 GPT-6.1 Sol
- 01
设置推理力度
建议从 medium 开始。对于需要先规划再回答的问题,可调高至 high、xhigh 或 max;当延迟比深度更关键时,可调低至 low。
- 02
发送 Prompt
请粘贴您的实际任务而非测试用例。每次响应下方都会显示 Token 用量和消耗的额度,以便您在正式接入前预估工作负载成本。
- 03
复制 API 调用代码
使用模型 ID gpt-6.1-sol 将相同的请求移至您的代码中。Chat Completions 和 Responses API 均支持工具调用(Tool calling)。
常见疑问
01GPT-6.1 Sol 在 AIReiter 上的费用是多少?
GPT-6.1 Sol 在 AIReiter 上的价格为每 100 万输入 tokens $0.60,每 100 万输出 tokens $3.00,仅为 OpenAI 官方价格($2.00 和 $10.00)的 30%。缓存输入读取费用为每 100 万 tokens $0.03(官方为 $0.10),缓存写入为每 100 万 tokens $0.75。超过 272K 输入 tokens 的请求按 2 倍输入和 1.5 倍输出费率计费。
02相比 GPT-6 Sol 有哪些变化?
基础输入和输出价格与 GPT-6 Sol 相同,但缓存输入价格减半,仅为未缓存费率的 5%(原为 10%)。推理力度(Reasoning effort)新增了 max 设置,同时不再支持 none 和 minimal 设置。上下文窗口、输出限制以及长上下文附加费保持不变。
03GPT-6.1 Sol 比 GPT-6 Astra 更好吗?
不是。Astra 仍然是 OpenAI 功能最强大的 GPT-6 模型,而 GPT-6.1 Sol 则低一个层级。选择 Sol 的核心优势在于成本:在短上下文情况下,其输入和输出价格仅为 Astra 的五分之一(每 100 万 tokens 输入为 $2 对比 $10,输出为 $10 对比 $50)。仅在 Sol 明显无法满足需求时才路由至 Astra。
04上下文窗口有多大?
GPT-6.1 Sol 拥有 1,050,000 个 token 的上下文窗口,最多支持 128,000 个输出 token,输入和输出共享该预算额度。在实际使用中,价格较低的部分为前 272K 输入 tokens:超过该限制后,整个请求将按 2 倍输入和缓存费率以及 1.5 倍输出费率计费。
05支持哪些推理力度(reasoning effort)设置?
GPT-6.1 Sol 支持 low、medium、high、xhigh 和 max,默认设置为 medium。部分早期 GPT 模型所支持的 none 和 minimal 设置在此不受支持。更高的设置会产生更多的推理 token(按输出计费),因此建议从 medium 开始,仅在需要规划的复杂问题上调高设置。
06GPT-6.1 Sol 支持工具调用吗?
支持。在 OpenAI 官方 API 上,GPT-6.1 Sol 仅支持通过 Responses API 进行工具调用,不支持 Chat Completions。而在 AIReiter 上,使用 gpt-6.1-sol 模型的工具调用在 https://aireiter.com/api/v1/chat/completions 和 https://aireiter.com/api/v1/responses 上均可正常运行,因此现有的 Chat Completions 工具调用循环无需任何更改即可继续使用。
07如何在 Codex CLI 中使用 GPT-6.1 Sol?
在 ~/.codex/config.toml 中添加 aireiter 提供商,将 base_url 设置为 https://aireiter.com/api/v1,wire_api 设置为 responses,env_key 设置为 AIREITER_API_KEY,然后将 model 设置为 gpt-6.1-sol。在环境变量中导出您的 AIReiter API Key 并启动 Codex。完整配置见上方的代码部分。
08GPT-6.1 Sol 何时发布?
OpenAI 于 2026 年 9 月 29 日发布了 GPT-6.1 Sol,作为 GPT-6 Sol 的升级版。付费计划用户可在 OpenAI API、ChatGPT Work 和 Codex 中使用。在 AIReiter 上,自发布起即可在 Playground 和 API 中使用,价格仅为官方每 token 单价的 30%。