OpenAI's Public Agent API: What the September 2026 Beta Costs and How It Compares

On September 10, 2026, OpenAI put its Codex coding-agent harness behind a single public agent API, in beta, with no platform fee beyond model tokens and the tools an agent actually calls.

The pitch is narrow but specific: building a reliable agent requires a harness that manages context, calls tools efficiently, coordinates subagents, and keeps state alive across sessions that can run for days — infrastructure most teams currently rebuild from scratch or buy from a framework vendor. OpenAI is now renting out the version it already built for its own products.

Public Agent API: What OpenAI Actually Shipped on September 10

OpenAI's public agent API is a managed service, in beta since September 10, 2026, that hands any developer the same session-management, sandboxing, and subagent-orchestration harness that runs Codex, OpenAI's own coding agent, behind a single API call. Instead of writing the plumbing that keeps an agent's context, files, and tool calls consistent across a multi-hour or multi-day task, a developer calls the API and lets OpenAI run that infrastructure.

The Four Objects the API Is Built From

Everything in the Agents API reduces to four pieces, according to OpenAI's own launch post and MarkTechPost's technical breakdown of the release:

Inside a live session, the API can run code, edit files, search the web, apply predefined skills, produce artifacts, and split work across subagents under a configurable concurrency limit — the same capability set Codex uses internally, according to MarkTechPost's reporting on the launch.

The Agent object's ability to connect to MCP servers is a quieter part of the announcement but arguably a load-bearing one. Model Context Protocol, the open standard Anthropic introduced in late 2024 for connecting AI systems to external tools and data, is now the common plumbing underneath both of OpenAI's agent products — the Agents SDK and the new Agents API — as well as Anthropic's own agent tooling. Cross-vendor tool compatibility is not the industry default, so a developer's MCP server built for one lab's agent product has a real chance of working unmodified against another's, which lowers the switching cost the rest of this piece argues OpenAI is otherwise trying to raise.

Where the Compute Actually Runs: 9 Partner Sandboxes

Developers choose where an agent's Environment executes: an OpenAI-managed sandbox, their own infrastructure, or one of nine named partner sandboxes — Blaxel, Cloudflare, Daytona, DigitalOcean, E2B, Modal, Oracle, Runloop, and Vercel. Each partner bills its own compute rates directly; OpenAI adds no markup on top.

That partner list is notable for one name in particular: Oracle is simultaneously a named sandbox partner and, according to MarkTechPost's reporting, one of OpenAI's own largest compute suppliers under the Stargate buildout — which puts OpenAI in the position of routing developer workloads to infrastructure it also buys from at massive scale.

The choice matters beyond raw price. A regulated enterprise that cannot send proprietary code or customer data into an OpenAI-controlled environment can pick a self-hosted sandbox, or a specific partner whose data-residency and compliance posture it already trusts, without losing the session-management and orchestration layer OpenAI still runs on top. That flexibility is the part of the pitch aimed less at indie developers and more at the enterprise buyers who were the actual holdout on adopting hosted agent infrastructure to begin with.

What Sandbox Time Actually Costs, Provider by Provider

OpenAI charges nothing extra for the Agents API itself, but the sandbox a developer picks still has its own bill. Here's what the researched partner and competitor pricing looks like as of September 2026 — every figure below comes from each vendor's own published pricing or vendor-pricing analysis, not from OpenAI.

Source: OpenAI Agents API announcement (Sept 2026); E2B published pricing, via Morph's E2B pricing breakdown; TrueFoundry's LangGraph pricing analysis; Upstash's agent sandbox provider comparison, 2026.

Agents API vs Agents SDK: Two Different Products, Same Name Confusion

The single most common mistake in early coverage of this launch is conflating the new Agents API with the existing OpenAI Agents SDK — they are genuinely different products built for different jobs. The Agents SDK is a free, MIT-licensed Python and TypeScript framework that launched in March 2025 as the production successor to OpenAI's experimental Swarm project. Its Runner executes the agent loop — tool calls, handoffs, guardrails — inside your own application and your own infrastructure; OpenAI updated it again in April 2026 with sandboxing support and provider-agnostic access to more than 100 LLMs beyond OpenAI's own models.

The Agents API is the opposite deployment model: OpenAI runs the session, the context compaction, and (optionally) the sandbox for you, and your application just calls the API and consumes the event stream. One is a library you embed and control; the other is infrastructure you rent. A team that wants full control over deployment, storage, and approval logic still reaches for the SDK. A team that wants to skip building session infrastructure altogether is who the API is for.

How the Field Compares: LangGraph, Vercel AI SDK, and Anthropic's Tool APIs

OpenAI isn't launching into an empty market. Three other paths already exist for a team that wants to ship an agent without hand-rolling infrastructure, and each takes a different bet on where the line between "framework" and "hosted service" should sit.

Source: OpenAI product documentation; TrueFoundry LangGraph pricing breakdown; Vercel AI SDK 6/7 release notes; Enterprise DNA reporting on Anthropic's August 2026 GA, 2026.

Anthropic has taken a noticeably different path than OpenAI's single-API bet: rather than bundling session, sandbox, and orchestration into one hosted "agent" object, Anthropic has been generally-availabling individual capabilities piecemeal — computer use and browser use moved out of beta on August 19, 2026, and self-hosted sandboxes with MCP tunnels shipped on May 19, 2026, letting enterprise teams keep execution on their own infrastructure while orchestration stays on Anthropic's platform. It's a more modular approach, and as of this writing there's no single Anthropic product that maps directly onto what OpenAI's Agents API bundles into one call.

Where the headline misses

The "no extra fee" framing that dominated launch-day coverage undersells what this move actually does. OpenAI isn't giving away infrastructure out of generosity — it's monetizing the layer underneath it more aggressively. Every workload that runs through the Agents API, including the tool calls, subagent turns, and context-compaction passes the harness generates automatically, consumes model tokens that OpenAI bills for. A framework that used to sit on top of a model API and take its own margin is now replaced by infrastructure that routes more spend directly to OpenAI's own models. That's a funnel into token revenue, not a free product.

There's also a real lock-in question the "$0 platform fee" pricing obscures. Once a team's session state, context-compaction logic, and subagent orchestration all live inside OpenAI's hosted harness rather than in code they control, switching to Claude, Gemini, or an open model later means rebuilding that plumbing from scratch — the exact cost the API is designed to make a developer forget about until they try to leave.

What This Means for Agent-Framework Startups

The competitive read that surfaced fastest after launch: OpenAI is competing directly with the field of agent-orchestration startups — LangChain, CrewAI, and a wave of smaller session-management layers — by commoditizing the exact harness those companies have been charging for. A framework whose entire pitch is "we handle session persistence and sandboxing so you don't have to" now has a much harder sell when the model vendor those agents already call gives that away as part of the API bill.

Early developer reaction on Hacker News mixed genuine interest with the same lock-in concern raised above: one recurring comment noted that OpenAI and Anthropic remain "stuck using their own proprietary frontier models," which for some multi-model teams outweighs the convenience of skipping the infrastructure build. Real independent adoption or usage numbers for the Agents API aren't available yet — it has been in public beta for under three weeks as of this writing, and neither OpenAI nor third-party trackers have published session-volume or developer-count figures. Any claim about how fast it's being adopted would be a guess, not a sourced fact.

For anyone evaluating agent-orchestration startups as an investment or a build-vs-buy decision, this launch is the cleanest test case available: how much of a portfolio company's retention was genuine workflow lock-in, specific integrations, vertical tuning, versus simply being the easiest way to get durable sessions and sandboxing before OpenAI shipped this API for free. Genuine workflow lock-in survives a launch like this one. Retention built only on convenience, now priced at a $0 platform fee, does not.