AI Launch Profile
OpenAI Assistants API migration deadline: August 26, 2026
OpenAI’s Assistants API reaches its shutdown deadline on August 26, 2026. OpenAI recommends Responses API and Conversations API, with documented mappings from Assistants to configuration or prompt structures, Threads to Conversations, Runs to Responses and Run Steps to Items.
At a glance
Launch Snapshot
- Company
- OpenAI
- Launch date
- August 26, 2026
- Launch type
- Not classified
- Category
- AI Agents, AI Developer Tools, AI Infrastructure
- Pricing
- There is no separate migration fee. Replacement API usage is billed under current OpenAI API pricing, while engineering, regression testing, data migration, observability and rollback work remain implementation costs.
- Free plan
- No
- API
- Yes
- Open weights/source
- No
Launch Context
Use these links to move from this record into the broader Launch Intelligence database.
Verification & Sources
- Status
- Verified
- Source links
- 6
- Freshness
- Verified July 28, 2026
- Last verified
- July 28, 2026
- Last updated
- July 28, 2026
Key source checks
Suggest a correction
Kingy AI Take
Treat August 26 as an operational deadline, not a feature launch or a find-and-replace exercise. OpenAI documents object and orchestration changes, including explicit tool-loop management and no automated Threads-to-Conversations migration. Teams should inventory live Assistants now, move new traffic first, regression-test state and tools, and retain a rollback path before the shutdown date.
Who it is for
Developers, agent teams, platform owners and engineering leaders responsible for production integrations that still use Assistants, Threads, Runs or Run Steps.
What feels promising
Responses and Conversations consolidate newer API behavior, while the migration guide gives teams a concrete mapping and examples for state, configuration and tool orchestration.
What feels unproven
Kingy did not migrate a production integration. Compatibility, stored-state transfer, prompt behavior, tool-call ordering, streaming, retries, background work and cost can differ by implementation and must be tested.
Source-backed record