Skip to content

OpenAI Responses API

OpenAI API endpoint (/v1/responses) for agentic apps, supporting server-side tool use, multi-turn state, and image generation; successor to Chat Completions.

Known aliases

  • B-resp transport
  • ChatGPT snippet
  • OpenAI Responses API
  • Responses API
  • Responses endpoint
  • /v1/responses
  • wire_api responses
  • Yanıtlar API'si

Current stories

buildConfirmed4 publishers

OpenAI splits classification into a Decisions API priced at 10 cents per million input tokens

OpenAI's Decisions API answers yes/no, pick-one and scale questions for $0.10 per million input tokens, with output free. Jev sells the same three question types for text at less than half that, so OpenAI's case rests on image input and compliance terms.

Perspective Coverage

4 publishers
Builder
Builder 59%
Operator
Operator 24%
Investor
Investor 17%

Reality

Evidence62
Adoption20
Hype gap+15
Incentives45
Confidence60
buildOne report1 publisher

Teams leaving OpenAI's retired Assistants API must rebuild thread history by hand

OpenAI retired the Assistants API on August 26, 2026, without an automatic tool to move old Threads into the Conversation objects that replace them. Teams that relied on managed threads now write that migration and set how much history each turn sends.

Publishers:dev.to

Reality

Evidence30
Adoption
Not scored
Hype gap+20
Incentives
Not scored
Confidence35
buildOne report1 publisher

Teams leaving Agent Builder must decide whether OpenAI or their own code runs the agent loop

OpenAI plans to shut down Agent Builder on November 30, 2026, so teams that built on it need another place to run their agent loops. The three OpenAI alternatives differ mainly in who runs that loop and who stores its state.

Publishers:dev.to

Reality

Evidence40
Adoption
Not scored
Hype gap+5
Incentives35
Confidence40
buildOne report1 publisher

Sign in with ChatGPT lets Plus and Pro users cover an app's AI requests from their own plan

OpenAI's Sign in with ChatGPT lets Plus and Pro users run an app's AI requests on their own plan, up to a weekly cap they set per app. That cap reserves none of the user's quota, so builders still need their own API key for any request the plan cannot cover.

Publishers:dev.to

Reality

Evidence55
Adoption30
Hype gap+5
Incentives30
Confidence50
buildOne report1 publisher

Changing only the model string to GPT-6.1 Sol leaves two broken fields in a coding agent's request

OpenAI's GPT-6.1 Sol halves old Sol's cache-read rate to $0.10 per million tokens and requires the Responses API for tool calls. In one worked example the cut saves about 10%, and older agents only get that saving after their tool and reasoning fields are rewritten.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap0
Incentives35
Confidence50
buildOne report1 publisher

Spring AI fixes its hard-coded 60-second stream timeout in a milestone release

Spring AI 2.0.1 ignores configured timeouts and kills any streaming turn longer than 60 seconds. The fix sits in 2.1.0-M1, a milestone built on Spring Boot 4.2.0-M2, so leaving the one-minute ceiling behind means running a pre-release stack.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+5
Incentives
Not scored
Confidence50
buildOne report1 publisher

A code-review agent read 9 files and hit 3 policy blocks before reporting success

One developer's harness logged 9 file reads, 7 processes and 3 policy blocks from a code-review skill that declared no file or process access. Pass/fail scoring loses those attempts, so the harness grades each run from raw traces and canaries checked against the environment.

Publishers:dev.to

Reality

Evidence30
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence35
buildConfirmed7 publishers

Multi-turn GPT Image 2.5 editing runs only through OpenAI's Responses API

OpenAI's guide names Sunburst for editing precision and Flare for speed, and both run from either API. The editing loop, File ID inputs and the action switch exist on the Responses side alone.

Perspective Coverage

7 publishers
Builder
Builder 62%
Operator
Operator 24%
Investor
Investor 14%

Reality

Evidence76
Adoption40
Hype gap+10
Incentives55
Confidence74
buildOne report1 publisher

Traffic past 15 requests a minute can route a prompt away from its cached prefix

OpenAI's guide prices reused input tokens at a discount of up to 90 percent. It also says cached key-value states sit on individual machines, so an unchanged prefix can still miss the cache when routing overflows.

Reality

Evidence58
Adoption
Not scored
Hype gap+10
Incentives75
Confidence65
buildOne report1 publisher

DeepSeek rejects the Codex turn where a resize notice separates a call from its output

Codex batched two view_image calls and put a resize notice between their outputs. OpenAI's Responses API pairs items by call ID wherever they sit. DeepSeek's endpoint wants them adjacent, and returns the same 400 on every later message.

Publishers:dev.to

Reality

Evidence62
Adoption22
Hype gap−8
Incentives32
Confidence58
scienceOne report1 publisher

UHP turns the choice of agent harness into a field in the request

The Unified Harness Protocol specifies how an application starts a task on an agent runtime, follows it, cancels it and collects the files, borrowing the shape of OpenAI's Responses API so existing streaming clients need no changes.

Publishers:unifiedharnessprotocol.org

Reality

Evidence32
Adoption
Not scored
Hype gap+35
Incentives62
Confidence52
buildOne report1 publisher

Whoever implements the server half of Responses picks your retrieval and veto defaults

The Responses and Messages dialects specify tool declarations, streaming and reasoning knobs. A Java 21 library published to Maven Central at 0.18.0 argues the unspecified half is where retrieval, injection and veto actually live, and offers to host it in your own process.

Publishers:dev.to

Reality

Evidence32
Adoption10
Hype gap+33
Incentives88
Confidence38
buildOne report1 publisher

Ollama's JSON decoder drops previous_response_id before any handler sees it

A single-box test on Ollama 0.34.0 shows a turn chained with previous_response_id coming back HTTP 200 and status completed at the same 41 input tokens as the same question sent with no history at all. The request struct has no field for the key.

Publishers:dev.to

Reality

Evidence66
Adoption26
Hype gap−8
Incentives22
Confidence63
buildOne report1 publisher

A 1.5x per-token price still bought a 25 percent cheaper correct answer in AWS's benchmark

AWS's open harness records $0.0021 per correct AIME answer for gpt-5.6-luna after an 80 percent Bedrock price cut. The figure depends on running luna with reasoning disabled while mini runs at its defaults.

Publishers:aws.amazon.com

Reality

Evidence58
Adoption
Not scored
Hype gap+15
Incentives80
Confidence55
buildOne report1 publisher

A previous_response_id continuation drops the instructions you set on turn one

OpenAI's create response reference is explicit that a chained request does not inherit earlier instructions, and because the field is optional, the turn that loses your JSON contract or your safety text still succeeds.

Publishers:dev.to

Reality

Evidence58
Adoption
Not scored
Hype gap+6
Incentives32
Confidence54
buildOne report1 publisher

A read-only MCP key drops the write tools out of tools/list

Once the client-side contract is a URL and a bearer header, nothing in your config records what that key may write. The decision moved to the mint screen, which is the screen easiest to skip.

Publishers:dev.to

Reality

Evidence32
Adoption20
Hype gap+15
Incentives82
Confidence48
buildOne report1 publisher

Bedrock turns GPT-5.6 throughput into a routing choice, with residency as the price

Cross-Region inference for GPT-5.6 on Amazon Bedrock means capacity ceilings are now fixed by changing a profile prefix, not by changing models. The tradeoff is where your data gets processed.

Publishers:aws.amazon.com

Reality

Evidence58
Adoption20
Hype gap+12
Incentives86
Confidence57
buildOne report1 publisher

Deferred tool schemas cut cost 21% on average, and made one task type 12.3% dearer

Progressive disclosure on a 20-tool agent saved about 30% of input tokens overall, but the per-task split shows cost stops being flat and starts tracking your traffic mix.

Publishers:dev.to

Reality

Evidence63
Adoption18
Hype gap−5
Incentives35
Confidence58