OpenAI removes the Assistants API on Wednesday, and the automations nobody owns go with it

Saturday and Sunday produced nothing in agentic payments I could date and verify. I ran the usual round this morning across the card networks, the processors, the protocol foundations and the regulators, and every item that came back was already in Friday’s brief or older than it. So this is a short edition about the one thing that is definitely happening this week, and it is a removal rather than a launch.

OpenAI shuts down the Assistants API on 26 August 2026. The date sits on OpenAI’s own deprecations page, with the Responses API and the Conversations API listed as the replacement [1], and the migration guide says it in one sentence: “It will shut down on August 26, 2026” [2].

That is Wednesday.

The part that costs is the part you did not write

Recreating an assistant as a Responses API call is an afternoon. The guide is candid about the rest of it. Threads do not come across on their own, and OpenAI writes that it “will not provide an automated tool for migrating Threads to Conversations” [2]. You either start conversations fresh or backfill the old ones yourself with the code examples provided [2].

Then there is orchestration. History pruning, tool loops and retries move out of the API and into your application code [2]. Those three were doing work nobody on your team ever wrote a ticket for, which is why they are absent from the estimate somebody gave you in March.

Azure retires its copy on the same day, to a different destination

A team that moved to Azure for procurement reasons does not get an extension. Microsoft’s own documentation says the Azure OpenAI “Assistants API is deprecated and will be retired on August 26, 2026”, and sends workloads to “the generally available Microsoft Foundry Agents service” [4].

Both retirements land on 26 August, and they point at different replacements, OpenAI at the Responses API and Microsoft at Foundry Agents. A shop running both clouds therefore has two pieces of work to do this week.

Where it actually bites

Your deployed code is the visible half. The other half is the automations somebody clicked together eighteen months ago and left running. Zapier is flat about the consequence, telling customers that “on August 26, 2026, Zaps using these actions will stop working” [3].

Exactly one action migrates automatically, Conversation With Assistant (Legacy). The ones that do not are Create Assistant, Upload File used with assistants, Find Assistant, Find or Create Assistant, List Assistants and List Assistant Files [3]. And the ones that do migrate arrive switched off, because “migrated Zaps are left turned off so you can review them first” [3].

Leaving them off is the right call by Zapier, and it is also the failure mode that nobody notices. A Zap that stops firing does not page anybody. It surfaces three weeks later as a customer asking why they never got the follow-up email.

What I would do today

Make two lists rather than one. The first is code you deploy, found by searching your repositories for the Assistants endpoints and the SDK helpers that wrap them. The second is everything else: Zapier, Make, internal scripts on somebody’s laptop, the workflow a contractor built for the operations team. The second list is the one that has no owner, and it is the reason the deadline is a Wednesday problem rather than an engineering-sprint problem.

If any Thread holds data you would miss, export it before Wednesday. There is no tool coming for it, and OpenAI has said so in writing [2].

A quiet weekend usually means a week with nothing in it. This one has a Wednesday.