Assistants API · removed 26 Aug 2026

Find out what actually broke.

Paste the code that stopped working. This page tags every line as dead, mapped, or needs judgment, and writes you a Responses API skeleton. It runs entirely in your browser — no key, no upload, no account.

Your code — Python or JavaScript

Nothing leaves this page.

Readout

0Dead — endpoint removed
0Mapped — mechanical swap
0Needs judgment

Line by line

Replacement skeleton


The mapped lines are the easy part.

A find-and-replace gets you the endpoint names. What it can't do is rebuild a tool loop that used to be handled by the run poller, decide which conversation history is worth carrying forward, or reason about a vector store your file search silently depended on. That's the part that takes a person, and it's the part that breaks in production a week later.

One warning worth having for free: most migration guides tell you to move your assistant config into Prompt Objects in the dashboard. Agent Builder and Prompt Objects sunset 30 November 2026. If you migrate that way you will do this again in three months. Keep your config in your own codebase.

$750Standard migration. Responses API + Conversations, tool loops rebuilt, working in 48 hours.
$1,500Vector stores plus custom function tools, or more than one service on the same broken integration.
Send your readout for a fixed quote