OpenAI debuts a Responses API to help developers build agents that search the web, scan for files, and perform tasks on PCs, and an Agents SDK for orchestration
But really, why isn't OpenAI building their own agents if their tech is so powerful? [embedded post] X: Atty Eleti / @athyuttamre : Introducing the Responses API: the new primitive of the OpenAI API. It is the culmination of 2 years of learnings designing the OpenAI API, and the foundation of our next chapter of building agents. 🧵Here's the story of how we designed it: [video] Simon Willison / @simonw : Wrote up some notes on the brand new OpenAI “Responses API”, launched this morning - which includes some fun new default tools for web search, vector-based RAG and tapping into their “computer use” remote controlled GUI computer environments https://simonwillison.net/... @yugacohler : The Crypto X AI narrative isn't just hype, it's very real. @CoinbaseDev AgentKit is a day 0 customer of thhe @openai Agents SDK, as announced in OpenAI's blog post today. Implementing onchain agentic actions is now trivial using the OpenAI AgentKit package. [image] @unifygtm : Unify's Agents now use @OpenAI's Computer Use! We've tested this model internally and are impressed by how it enables Agents to interact with the web and access previously unreachable information. With Computer Use, our Agents can surface any buyer signal with precision and [image] Elvis / @omarsar0 : NEW: OpenAI announces new tools for building agents. Here is everything you need to know: [image] Kyle Corbitt / @corbtt : This API shape is genuinely much nicer than the Chat Completions one. Just wish we could fast-forward 24 months into the future and skip the part where we'll have to support both APIs for every feature! @openaidevs : We're launching new tools to help developers build reliable and powerful AI agents. 🤖🔧 Timestamps: 01:54 Web search 02:41 File search 03:22 Computer use 04:07 Responses API 10:17 Agents SDK [video] Simon Willison / @simonw : Today in definitions of “agent”, we had: 1. “systems that independently accomplish tasks on behalf of users” 2. “LLMs equipped with instructions and tools” Both from @OpenAI - the first from their blog post, the second from the docs for their new OpenAI Agents SDK Sam Altman / @sama : this is a tremendous accomplishment from the team. i am obviously biased but i think it's one of the most well-designed and useful APIs ever, and that people will really love it. @openaidevs : Our new API primitive: the Responses API. Combining the simplicity of Chat Completions with the tool-use of Assistants, this new foundation provides more flexibility in building agents. Web search, file search, or computer use are a couple lines of code! https://platform.openai.com/ ... [video] Tibor Blaho / @btibor91 : Summary of insights from today's OpenAI AMA on X following the launch of Agent Tools and APIs (March 11, 2025) Responses API and Tools - Operator functionality (CUA model) is available starting today through the Responses API - Responses API is stateful by default, supports Aaron Levie / @levie : Multi-Agent workflows are the future of AI. OpenAI released new Agent APIs today, and Box built an Agent that combines documents from Box and web search tools to generate answers. Enterprise devs can grab sample code from our GitHub repo to customize with their data. [video] Simon Willison / @simonw : New openai-agents Python library https://github.com/... Simon Willison / @simonw : The problem with much of the AI world deciding to ship cloned versions of the OpenAI API - we've seen that from Ollama and Mistral and DeepSeek and Gemini and Anthropic and more... is what happens when OpenAI decide to redesign their API entirely? Simon Willison / @simonw : New from OpenAI today: the Responses API! Here's their documentation about how it differs from the Chat Completions API that everyone has cloned already https://platform.openai.com/ ... LinkedIn: Michael Albada : OpenAI just launched the Agents SDK. We've known that they have been working on this behind the scenes, and it's great to finally get to see it. … Forums: r/ChatGPT : OpenAI dropped new tools to build Agents r/OpenAI : New tools for building agents Ars OpenForum : OpenAI pushes AI agent capabilities with new developer API
Context & Ripple Effects
OpenAI had already exposed agent behavior directly to users through its Operator research preview, while its earlier SearchGPT effort established web search as a core AI capability. The Responses API brings those capabilities into a developer-facing primitive rather than leaving them as standalone product features.
The move also foreshadows OpenAI's later AgentKit packaging for building and deploying agents and an Apps SDK built on MCP. Together, the coverage traces a shift from individual agent tools toward a platform stack for third-party agent development.
First-order effects
- Developers can build on one API surface for web search, file search, computer use, and retrieval, while the Agents SDK supplies orchestration scaffolding that would otherwise be custom application work.
- Early adopters such as Coinbase, Unify, and Box can connect agent workflows to their own products and data sources using OpenAI-provided tools rather than assembling every capability independently.
Second-order effects
- Agent builders face a clearer build-versus-buy choice: OpenAI's bundled tools can shorten implementation time, but applications that need distinctive behavior may still differentiate through workflow design, data access, and controls.
- Computer-use support broadens the addressable set of browser- and desktop-mediated workflows, putting pressure on adjacent automation products to show stronger reliability, integration depth, or governance.
Third-order effects
- If tool access and orchestration continue to standardize, agent development is likely to move from bespoke model integrations toward reusable application layers—an app ecosystem built around common agent interfaces rather than isolated chat experiences.
- The lasting competitive boundary may shift toward ownership of enterprise context, permissions, and workflow integration; the supplied model and tools become more interchangeable components, though deployment safety remains a constraint.
The trend: This is one step in the conversion of frontier-model capabilities into a full developer platform for embedded, workflow-specific agents.