SHUTDOWN IN EFFECT OpenAI Assistants API — removed 2026-08-26 App down? Migrated in 48 hours.
SUNSET_AUDIT

INCIDENT REPORT // SHUTDOWN IN EFFECT

On August 26, your AI assistant stopped answering.

OpenAI has permanently shut down the Assistants API. Every call to /v1/assistants, /v1/threads and /v1/runs now returns a hard error — and every Zapier Zap built on ChatGPT Assistants steps went dark the same day. Not degraded. Dark.

FREE Not sure what broke? The break check tags every dead line in your browser — no key, no signup.

DEPRECATION SCHEDULE — OFFICIAL, NOT RUMOR

DATE
WHAT DIES
AUG 26
Assistants API — full removal. Apps, custom chatbots, and all Zapier "ChatGPT (Assistants)" steps now fail.
NOV 30
Agent Builder, Evals & dashboard Prompt Objects — shut down. (Migrating to Prompt Objects is a second dead end — most plans miss this.)
DEC 1
Older GPT Image models removed from the API.

Source: OpenAI official deprecations page — verify yourself at developers.openai.com/api/docs/deprecations

Your app went dark on Aug 26 if any of these is true

  • [ ✕ ] A freelancer or agency built you a "custom GPT chatbot" in 2023–2025 and you haven't touched the code since.
  • [ ✕ ] Your Zapier account has Zaps using ChatGPT (Assistants) steps — lead replies, support triage, content pipelines.
  • [ ✕ ] You built client workflows in Agent Builder (launched Nov 2025, shutting down Nov 30 — see below).
  • [ ✕ ] Your codebase contains openai.beta.assistants or openai.beta.threads anywhere.

If you don't know what broke, the free break check tells you, line by line, in your browser — then we migrate it.

PROOF — NOT A TEMPLATE

See a real audit before you pay for one.

Here's an actual Break-Check Audit run against a real open-source chatbot platform built on the Assistants API. Nine doomed call sites across five files, conversation history at risk in the database, a migration map, and a fixed quote — exactly what you receive, in your inbox, within 48 hours.

READ THE SAMPLE AUDIT (PDF)

Fixed price. Fixed scope. Back online in 48 hours.

No hourly billing, no retainers. You know the cost before we start.

EMERGENCY MIGRATION

Responses + Conversations

$750

  • · Assistants → Responses API + Conversations
  • · Tool loops rebuilt — the run poller has no drop-in replacement
  • · Config kept in your code, not dashboard Prompts (which also die Nov 30)
  • · Working in 48 hours
START EMERGENCY MIGRATION

ADVANCED

Vector stores + custom tools

$1,500

  • · Vector stores plus custom function tools
  • · Or more than one service on the same broken integration
  • · Conversation history preserved where it exists, behavior-parity tests included
  • · Quoted exactly after we scope it — no surprises
REQUEST A QUOTE

Payment by PayPal invoice (international) — sent after we scope your audit. No card details entered on this site.

WHO YOU'RE WORKING WITH

Imran & a small migration team

I lead the engagement — scoping and de-risking the migration, the part where most projects go wrong — backed by a small team of developers, architects and analysts who do the code work. You deal with one point of contact (me), not a ticket queue.

This shutdown is a clean, bounded problem: a fixed set of retired endpoints, a known replacement, a hard date. We read your code or your Zaps, tell you in plain language what breaks and when, and hand you a fixed price to fix it — with a parity test log and handover docs your next developer will thank you for. Modern AI-assisted tooling is part of how we turn a 48-hour audit around reliably without inflating the price.

HOW IT RUNS

From email to "back online"

  1. T-0 You email read access — code, Zapier screenshots, or a screen-share.
  2. T+48h Emergency migration delivered — Responses + Conversations, tool loops rebuilt, tested side-by-side. PayPal invoice.
  3. LIVE Your assistant answers again. RESOLVED

GET STARTED

Send one message. Tell us what broke — we'll tell you the fix.

Typical reply time: same day (IST business hours).