OpenAI embraces the 'platform paradox' by selling API access to startups that compete directly with its own apps like ChatGPT. The strategy is to foster a broad ecosystem, believing that enabling competitors is necessary to avoid losing the platform race entirely.

OpenAI integrated the Model-Centric Protocol (MCP) into its agentic APIs instead of building its own. The decision was driven by Anthropic treating MCP as a truly open standard, complete with a cross-company steering committee, which fostered trust and made adoption easy and pragmatic.

AI platforms using the same base model (e.g., Claude) can produce vastly different results. The key differentiator is the proprietary 'agent' layer built on top, which gives the model specific tools to interact with code (read, write, edit files). A superior agent leads to superior performance.

Companies can build authority and community by transparently sharing the specific third-party AI agents and tools they use for core operations. This "open source" approach to the operational stack serves as a high-value, practical playbook for others in the ecosystem, building trust.

In a significant strategic move, OpenAI's Evals product within Agent Kit allows developers to test results from non-OpenAI models via integrations like Open Router. This positions Agent Kit not just as an OpenAI-centric tool, but as a central, model-agnostic platform for building and optimizing agents.

The IDE Zed was built for synchronous, Figma-like human collaboration to overcome asynchronous Git workflows. This foundation of real-time, in-code presence serendipitously created the perfect environment for integrating AI agents, which function as just another collaborator in the same shared space.

Using a composable, 'plug and play' architecture allows teams to build specialized AI agents faster and with less overhead than integrating a monolithic third-party tool. This approach enables the creation of lightweight, tailored solutions for niche use cases without the complexity of external API integrations, containing the entire workflow within one platform.

Instead of relying on a single, all-purpose coding agent, the most effective workflow involves using different agents for their specific strengths. For example, using the 'Friday' agent for UI tasks, 'Charlie' for code reviews, and 'Claude Code' for research and backend logic.

Stripe intentionally designed its Agentic Commerce Protocol (ACP) to be provider-agnostic, working with any payments processor and any AI agent. This strategic decision to build an open standard, rather than a proprietary product, aims to grow the entire agentic commerce ecosystem instead of creating a walled garden.