OpenAI NewsMar 11, 2025, 18:00 UTC+8

New tools for building agents

OpenAI released the Responses API, three built-in tools, and an Agents SDK on March 11, 2025 for single-agent and multi-agent workflows. The post confirms web search, file search, and computer use, says the API is available to all developers today, and says billing stays at standard token and tool rates. The key platform signal is migration: OpenAI plans an Assistants API sunset in mid-2026 after full feature parity with Responses API.

Why it matters: This is a substantive OpenAI developer-platform launch, not a routine feature add. HKR-H/K/R all pass: new entry point, concrete tools and pricing, plus a sunset timeline that will affect agent frameworks and API choices immediately.

Read the original ↗Export Markdown

Take

OpenAI is pulling the agent stack back behind one main API, reducing developer glue while taking more runtime control. Responses API is available to all developers on day one, with web search, file search, and computer use built in. There is no separate API fee, but tokens and tools still meter usage. That is the classic platform move: remove integration pain first, then make retrieval, browser control, tracing, and evals native billable surfaces.

The sharper line is the Assistants API sunset target in mid-2026 after feature parity. The Agents SDK headline is fine, but the migration clock is the power move. Teams spent the last year wiring LangGraph, LlamaIndex, CrewAI, custom queues, and observability around tool calls. OpenAI is saying those layers belong closer to its runtime. I buy the direction, but I would not rip out external orchestration until parity and failure-mode visibility are proven in production.

Source: OpenAI News · openai.com
Published: Mar 11, 2025, 18:00 UTC+8 · Mar 11, 2025