Fix OpenAI Responses API tool-call 400s, wrong call_id errors, truncated JSON, and invalid_json_schema failures in Python and TypeScript.

Fix OpenAI Assistants API sunset migration failures by converting Threads and Runs to Conversations and Responses without losing history, images, or tool calls.

Learn how startups use GPT-5.6 to build faster, more cost-efficient AI agents with smarter model selection and new Responses API capabilities.

SentinelLABS evaluated OpenAI's native Responses API compaction for long-running malware analysis workflows and found it cut input tokens by about 86% with no measurable change in overall evaluation score. The study concluded that compaction can reduce noise and cost while preserving task quality, though it may slightly weaken domain object modeling in some cases. #OpenAI #ResponsesAPI #SentinelLABS

Cross-linking — we’re seeing the same duplicate/similar output within a single response on **gpt-5.5 (thinking)** via the Responses API. A cross-model A/B isolates it to gpt-5.5 (gpt-4.1 0/30, claude-sonnet-4-6 0/30), and token billing confirms the model itself generates the second copy — clean openings bill ~77–93 output tokens, doubled ones ~130–258. Consolidated evidence: Regression: Double responses in apps Happy to share request IDs / a sanitized payload.

Hi, there. I have been using gpt-4.1 model for ResponsesAPI to implement web search with OpenAI and it has been working properly. Once GPT-5.2 model is launched, I have upgraded the model to GPT-5.2. But it seems like it’s not enabled to do web search. When asking “Can you do web search“ for GPT-4.1 model, it worked great but for GPT-5.2, it’s not working. Also, my agent is asking any additional data source instead of doing web search internally. I hope you please help me to fix this. Thank you.

There is a bug in ResponsesApi. I don’t send top_p in payload, but error is the result.

I’m experiencing the exact same issue on my client implementation. With the ResponsesAPI, file citations only map back to the file level, not the specific chunk returned by the `file_search` tool. In the AssistantsAPI, we were able to link citations directly to the chunk used in the answer, which is essential for our UX. Is there currently any way to retrieve or correlate the chunk associated with a given annotation? Or is this functionality no longer supported in the new API?

We are in the process of migrating our application from using AssistantsAPI to ResponsesAPI. When using the file_seach tool with ResponsesAPI, the relevant output looks like the following: { “type”: “response.output_item.done”, “sequence_number”: 8, “output_index”: 1, “item”: { “id”: “fs_id”, “type”: “file_search_call”, “status”: “completed”, “queries”: [ “query1”, “query2”, ], “results”: [ { “attributes”: {}, “file_id”: “file_id”, “filename”: “filename.pdf”, “score”: 0.6731, “text”: “chunk text”, “vector_store_id”: “vs_id” }, { “type”: “response.output_text.annotation.added”, “sequence_number”: 656, “item_id”: “item_id”, “output_index”: 3, “content_index”: 0, “annotation_index”: 18, “annotation”: { “type”: “file_citation”, “file_id”: “file_id”, “filename”: “filename.pdf”, “index”: 3320 } } “type”: “response.content_part.done”, “sequence_number”: 711, “item_id”: “item_id”, “output_index”: 3, “content_index”: 0, “part”: { “type”: “output_text”, “annotations”: [ { “type”: “file_citation”, “file_id”: “file_id”, “filename”: “filename.pdf”, “index”: 438 },] This does not allow tying back an annotation to a specific chunk, only to a specific file. We’d like to expose to our users the specific chunk that was used to answer the question, not just the file. In AssistantsAPI this is a functionality we had, and we’d like to keep it the same. Is there a configuration setting or something else we’re missing or is this simply not possible with ResponsesAPI?

Hey @jasondouglas , we’ve also been experiencing this issue. Almost 1 out of every 20 of our responses in the last 48 hours have had duplicate/similar output text within the same response. Could we be opted in to the fix as well? happy to followup wherever is appropriate with details Thanks!

My team is also seeing this behavior, and spun our wheels for days trying to diagnose. Since we are managing our own conversation state, we were thinking of switching back to the Completions API.

Hi @stevecoffey this is still happening for me and I have logs and everything ready if you want to take a look. We are observing this quite frequently.

It would not be reproducible exactly - you guys shut the gpt-4.5 model off. Here’s a forum topic to follow up on, along with others on the forum with similar symptom of also repeating structured outputs where the JSON restarts. How to prevent the API returning multiple outputs? API > I am using the responses API with file search. However, sometimes it creates 2, and sometimes even 15+ output messages. Even in the Logs page on the dashboard I see that the assistant sent 15 similar messages in a row and it eats tokens like crazy. I have tried setting parallel_tool_calls to false, yet it still creates multiple output messages (with the same message ID). Is there a way to force it to create only one output? There doesn’t seem to be any “output count limit” in the API docume… Seems it is an issue with the model not emitting the correct stop sequence token, or the API endpoint not catching it correctly, as it seems symptomatic on the Responses endpoint.

Hey @mhjacobson and @IM-TRB6 – Steve here from the API engineering team. Can you confirm if this is still occurring, and if so, if you have a short repro you can provide? Thank you for letting us know!

Not getting any errors, but every request to `gpt-5` with basic `medium` will reason through a ton of tokens, but then no final output. This is with the ResponsesAPI. I would occasionally get a response after several minutes last night, but now its producing nothing.

Came here looking for similar – what the heck? Woke up this morning, ResponsesAPI is not responsing… (nothing on status.openai)

I’m hitting a similar issue (GPT 4.1) but as we were able to migrate to the ResponsesAPI, just wondering if we should handle a workaround on our end or if OpenAI already fixed it in the new API.

Actually you are on to something and didn’t get you wrong so all good there! I just noticed this : OpenAI compatibility  |  Gemini API  |  Google AI for Developers so my plans change yet again and this calls for a heads down hackathon with my team while we support ongoing customers. Thank you for asking the tough questions. I slightly agree to disagree on the ease of use with responsesAPI, I am a lone developer and cobbled everything together with chatCompletions and hence I don’t want to change it unless I have to! However, a lot of naive software developers - fresh grads/seasoned folks new to AI want to start with something simple to grasp the concepts in detail so it’s a human / talent question - there is a huge gap between folks who started developing since gpt3.5 vs now and that slows down momentum in going to market and getting revenue.

kavitatipnis: > I am unclear on what you mean by proprietary corner ? The Responses API is the proprietary corner. Currently you can switch models easily to other providers using Chat Completions. (don’t get me wrong, I’m a huge OpenAI fan and user, but I’m also keen on good strategy) kavitatipnis: > Proprietary is where the new AI Platforms ( LLM OS concept) is headed I’m not sure I’d agree with you. Yes, OpenAI is trying to see if that’s possible. kavitatipnis: > responsesAPI offers a few capabilities natively which involves less overhead if you are a really tiny startup. Seriously, I’m a single developer and have written two Chatbots with web search and web crawl with just Chat Completions (and loads of complex behaviour in addition). It’s a non-issue. kavitatipnis: > Using any model via LiteLLM - OpenAI Agents SDK I’m actually a contributor to that project (albeit one PR )