2026-10-11 17:10 UTC

OpenAI claims its Agents API public beta exposes the managed Codex harness with durable sessions, context compaction, recovery, and subagents across hosted and developer-controlled execution environments, reducing the orchestration infrastructure developers must build themselves.

state: corroboratedheat: lowuncertainty: lowconvergesscott: mediumagent-harnesses agent-orchestration llm-apisOpenAI
Surfaced 2026-09-20T09:26:37Z — OpenAI introduces the Agents API; the accompanying documentation and Reddit account describe managed Codex orchestration with durable sessio — The sustained, top-decile spread across platforms warrants higher attention even though the latest spike adds no substantive evidence: attention to this episode is broader than its independent validation. The build-versus-adopt question now carries a prominent compute-lifecycle warning, not proof of systemic billing failure or independently demonstrated orchestration savings.

What is this?

OpenAI released its Agents API into public beta on September 10, 2026, exposing the managed 'Codex harness' — the orchestration runtime behind its Codex coding agent — as a cloud service that handles durable, resumable long-running sessions, automatic context compaction, recovery, tool search, programmatic tool calling, MCP integration, and parallel subagent delegation. Developers choose among OpenAI-hosted sandboxes, their own infrastructure, or partner sandbox environments (Cloudflare, Modal, Vercel, DigitalOcean, Daytona, E2B, Runloop), and pay standard rates for model tokens, tools, and container time with no separate platform fee — but session state remains OpenAI-managed with US-only residency and no Zero Data Retention support, and the managed API is distinct from the open-source Agents SDK. The supplied coverage is consistent on these launch claims (vendor testimonials of cost/latency gains remain unreplicated) but silent on the billing incident the case record tracks: a reported $1,600 idle-container bill that became an OpenAI-acknowledged billing defect (user-posted email plus status incident edx5g3vm), confirming a real beta-stage compute-lifecycle failure mode while bounding it as owned and remediated.

Why it matters to Scott

OpenAI has productized as a managed API precisely the durable-state/compaction/recovery architecture of Scott's Long-Running Agents framework, making this a live build-versus-adopt decision against the Proposal Compiler's custom FastAPI session-recovery control plane; the now OpenAI-acknowledged idle-container billing defect is a dated receipt for his billing-visibility doctrine (token spend is not total cost; managed orchestration does not remove compute-lifecycle management), and OpenAI-held session state with no ZDR even on self-hosted compute keeps the vendor-lock-in edge real. Remains medium rather than high: recovery guarantees, compaction fidelity and workload-specific TCO are still unvalidated and vendor testimonials unreplicated, so the case sharpens his evaluation criteria rather than changing what he builds today.
ip:framework.long-running-agentsdev:project.proposalip:framework.context-engineeringdev:concept.agent-authored-context-compactionip:concept.vendor-lock-inip:concept.token-economicsradar:concept.agent-harnessesradar:concept.long-running-agentsradar:concept.context-compactionradar:concept.inference-economicsradar:codex-bedrock-billing-overchargeradar:claude-phantom-token-billing-bugradar:docker-cloud-sandboxes-release
queries asked of Scott's wikis
  • long-running agent continuity session recovery requirements
  • Proposal Compiler custom session recovery machinery
  • agent harness design control loop context compaction
  • build versus adopt managed orchestration vendor lock-in
  • agent compute spend container cost billing visibility
  • subagent delegation multi-agent orchestration patterns

Measured heat

now 0 pts/hpeak 1 pts/hcomments 0/hpeers p14momentum: steady4 platformsage 760h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion

How the heat travelled

09-10 20:34 (minted)⭐ origin echo-reconstructedOpenAI introduces the Agents API; the accompanying documentation and Reddit account describe managed Codex orchestration with durable sessio
OpenAI on blog (echo) · attributed from reddit.post.1wctpbu, hn.story.49649213, hn.story.49648985 · published time unknown
—
09-10 00:00first on openai · published · lag ?Introducing the Agents API
OpenAI
—
09-10 19:22first on hacker news · published · lag ?OpenAI Agents API
ushakov
—
09-10 19:46first on r/artificial · published · lag ?OpenAI launches Agents API public beta built on Codex harness
Codeblix_Ltd
—
09-18 19:01first on r/OpenAI · published · lag ?Be careful with the new Agents API, I just paid $1600 for idle containers
Wide-Arugula3042
—
09-10 19:22amplified on hacker newshn.story.49648985
ushakov
peak 13 · 0 comments · 2% of case engagement
09-10 19:43amplified on hacker news 👑hn.story.49649213
aquir
peak 350 · 185 comments · 75% of case engagement
09-10 19:46amplified on r/artificialreddit.post.1wctpbu
Codeblix_Ltd
peak 7 · 13 comments · 2% of case engagement
09-11 12:43amplified on hacker newshn.story.49657480
ltononro
peak 2 · 0 comments · 0% of case engagement
09-18 14:35amplified on r/artificialreddit.post.1wjrxdf
ksraj1001
peak 1 · 0 comments · 0% of case engagement
09-18 19:01amplified on r/OpenAIreddit.post.1wjz5ze
Wide-Arugula3042
peak 149 · 39 comments · 15% of case engagement
3 more amplifiers in ainews.case_chain
09-10 20:21our radar first saw it · lag ?discovery anchor: reddit.post.1wctpbu—
09-20 09:26reached heat=high · lag ? · via ledger——
pace: p90 vs 519 stories at the 720h mark (now 760h old) — ahead of identity-verification-live-feed-breach (1.0x), behind llama-cpp-hot-swappable-ple-memory (0.9x)

Evidence (11) — ⭐ canonical anchor

sourceobjectauthorscorecomments
🟠 redditOpenAI launches Agents API public beta built on Codex harness
artificial
Codeblix_Ltd413
🟧 hnOpenAI Agents API
Retrieved article excerpt

Open article · Retrieved 2026-09-10T20:24:49.546675+00:00

The Agents API gives your application access to the Codex harness through an OpenAI-managed API. OpenAI manages sessions, orchestration, context compaction, and recovery while your application provides tools and chooses its execution environment. Agents can operate in a sandbox where they can execute code, edit files, connect to MCP servers, and produce artifacts. Pricing Model usage is billed at the selected model’s API rates . OpenAI tools use their standard rates , and OpenAI-hosted sandboxes use standard container rates . Try an example Try these complete examples: Create and run a directory-tree script in an OpenAI-hosted sandbox. Compare release notes with subagents and combine their findings into one answer. Explore complete applications: Incident response agent : investigate alerts and request approval for recovery actions. Slack bot : investigate requests using connected workplace tools. Data analyst : answer warehouse questions with read-only SQL. GitHub issue investigator : reproduce reported bugs and share findings on GitHub. Document reviewer : review documents with policy skills and specialist agents. Core concepts The Agents API is built around four main concepts: Agent: The model, instructions, tools, and MCP servers available to the agent. Environment: An optional sandbox or computer where the agent accesses files, loads skills, and runs commands. Session: A durable instance of an agent that works on tasks and responds to input. Events and items: The inputs sent to an agent and the output produced during a session. A session from start to finish Start with an OpenAI-hosted sandbox in the quickstart : Create a session. Configure the agent; OpenAI provisions its environment. Give it a task. User input starts a turn of work once the environment is ready. Follow progress. Stream output or use webhooks to learn when the agent finishes or needs input. Continue or steer. Send another task to the same session, or guide the agent during its current turn. With an OpenAI-hosted session, your application sends input and receives events, while OpenAI runs the agent and provisions and manages its sandbox. See environment options for setup and limitations. What the managed harness provides The managed Codex harness supports: Running commands and code in a sandbox. Applying relevant skills and instructions. Connecting to external data through tools or MCP. Steering the agent while it works. Summarizing previous work to manage its context window. Breaking work into subtasks and delegating to subagents. Resuming a session where it left off. Check the quickstart prerequisites for API-key permissions and SDK setup. Configure these capabilities when you create a session: Configure managed-harness capabilities Python 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 import OpenAI from "openai"; const client = new OpenAI(); const session = await client.beta.agents.sessions.create({ agent: { model: "gpt-6-astra", instructions: "Use the OpenAI documentation MCP and web search to answer technical questions accurately. Delegate independent research tasks to subagents when useful.", tools: [ { type: "programmatic_tool_calling" }, { type: "mcp", server_label: "openai_docs", transport: { type: "http", server_url: "https://developers.openai.com/mcp", }, }, { type: "web_search" }, ], multi_agent: { enabled: true, max_concurrent_subagents: 4 }, }, environment: { type: "self_hosted", workspace_directory: "/workspace", capability_directories: ["/workspace/capabilities/skills"], }, input: [ { role: "user", content: [ { type: "input_text", text: "Research how to connect an MCP server to an OpenAI agent, check for recent updates, and summarize the recommended setup.", }, ], }, ], }); console.log(session.id); 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 from openai import OpenAI client = OpenAI() session = client.beta.agents.sessions.create( agent = { "model" : "gpt-6-astra" , "instructions" : "Use the OpenAI documentation MCP and web search to answer technical questions accurately. Delegate independent research tasks to subagents when useful." , "tools" : [ { "type" : "programmatic_tool_calling" }, { "type" : "mcp" , "server_label" : "openai_docs" , "transport" : { "type" : "http" , "server_url" : "https://developers.openai.com/mcp" , }, }, { "type" : "web_search" }, ], "multi_agent" : { "enabled" : True , "max_concurrent_subagents" : 4 }, }, environment = { "type" : "self_hosted" , "workspace_directory" : "/workspace" , "capability_directories" : [ "/workspace/capabilities/skills" ], }, input = [ { "role" : "user" , "content" : [ { "type" : "input_text" , "text" : "Research how to connect an MCP server to an OpenAI agent, check for recent updates, and summarize the recommended setup." , } ], } ], ) print (session.id) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 import ( "context" "fmt" "github.com/openai/openai-go/v3" ) ctx := context.Background() client := openai.NewClient() session, err := client.Beta.Agents.Sessions.New(ctx, openai.BetaAgentSessionNewParams{Agent: openai.BetaAgentSessionNewParamsAgent{Model: openai.String("gpt-6-astra"), Instructions: openai.String("Use the OpenAI documentation MCP and web search to answer technical questions accurately. Delegate independent research tasks to subagents when useful."), Tools: []openai.AgentToolParamUnion{openai.AgentToolParamUnion{OfParamProgrammaticToolCalling: &openai.AgentToolParamProgrammaticToolCalling{}}, openai.AgentToolParamUnion{OfParamMcp: &openai.AgentToolParamMcp{ServerLabel: "openai_docs", Transport: openai.McpTransportParamUnion{OfParamHTTP: &openai.McpTransportParamHTTP{ServerURL: "https://developers.openai.com/mcp"}}}}, openai.AgentToolParamUnion{OfParamWebSearch: &openai.AgentToolParamWebSearch{}}}, MultiAgent: openai.MultiAgentConfigParam{Enabled: true, MaxConcurrentSubagents: openai.Int(4)}}, Environment: openai.EnvironmentParamUnion{OfParamSelfHosted: &openai.EnvironmentParamSelfHosted{WorkspaceDirectory: "/workspace", CapabilityDirectories: []string{"/workspace/capabilities/skills"}}}, Input: openai.BetaAgentSessionNewParamsInputUnion{OfArrayOfInputMessages: []openai.AgentSessionInputMessageParam{openai.AgentSessionInputMessageParam{Content: []openai.InputContentParamUnion{openai.InputContentParamUnion{OfParamInputText: &openai.InputContentParamInputText{Text: "Research how to connect an MCP server to an OpenAI agent, check for recent updates, and summarize the recommended setup."}}}}}}}) if err != nil { panic(err) } fmt.Println(session.ID) 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 import com.openai.client.OpenAIClient; import com.openai.client.okhttp.OpenAIOkHttpClient; import com.openai.models.beta.agents.AgentToolParam; import com.openai.models.beta.agents.EnvironmentParam; import com.openai.models.beta.agents.McpTransportParam; import com.openai.models.beta.agents.MultiAgentConfigParam; import com.openai.models.beta.agents.sessions.SessionCreateParams; import java.util.List; OpenAIClient client = OpenAIOkHttpClient.fromEnv(); var session = client .beta() .agents() .sessions() .create( SessionCreateParams.builder() .agent( SessionCreateParams.Agent.builder() .model("gpt-6-astra") .instructions( "Use the OpenAI documentation MCP and web search to answer" + " technical questions accurately. Delegate independent" + " research tasks to subagents when useful.") .addTool(AgentToolParam.ProgrammaticToolCalling.builder().build()) .addTool( AgentToolParam.Mcp.builder() .serverLabel("openai_docs") .transport( McpTransportParam.Http.builder() .serverUrl("https://developers.openai.com/mcp") .build()) .build()) .addTool(AgentToolParam.WebSearch.builder().build()) .multiAgent( MultiAgentConfigParam.builder() .enabled(true) .maxConcurrentSubagents(4L) .build()) .build()) .environment( EnvironmentParam.SelfHosted.builder() .workspaceDirectory("/workspace") .capabilityDirectories(List.of("/workspace/capabilities/skills")) .build()) .input( "Research how to connect an MCP server to an OpenAI agent, check for recent" + " updates, and summarize the recommended setup.") .build()); System.out.println(session.id()); 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 require "openai" client = OpenAI::Client.new session = client.beta.agents.sessions.create(agent: {model: "gpt-6-astra", instructions: "Use the OpenAI documentation MCP and web search to answer technical questions accurately. Delegate independent research tasks to subagents when useful.", tools: [{type: "programmatic_tool_calling"}, {type: "mcp", server_label: "openai_docs", transport: {type: "http", server_url: "https://developers.openai.com/mcp"}}, {type: "web_search"}], multi_agent: {enabled: true, max_concurrent_subagents: 4}}, environment: {type: "self_hosted", workspace_directory: "/workspace", capability_directories: ["/workspace/capabilities/skills"]}, input: [{role: "user", content: [{type: "input_text", text: "Research how to connect an MCP server to an OpenAI agent, check for recent updates, and summarize the recommended setup."}]}]) puts session.id 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 curl -sS -X POST "https://api.openai.com/v1/agents/sessions" \ -H "OpenAI-Beta: agents=v1" \ -H "Authorization: Bearer $OPENAI_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "agent": { "model": "gpt-6-astra", "instructions": "Use the OpenAI documentation MCP and web search to answer technical questions accurately. Delegate independent research tasks to subagents when useful.", "tools": [ { "type": "programmatic_tool_calling" }, { "type": "mcp", "server_label": "openai_docs", "transport": { "type": "http", "server_url": "https://developers.openai.com/mcp" } }, { "type": "web_search" } ], "multi_agent": { "enabled": true, "max_concurrent_subagents": 4 } }, "environment": { "type": "self_hosted", "workspace_directory": "/workspace", "capability_directories": ["/workspace/capabilities/skills"] }, "input": [ { "role": "user", "content": [ { "type": "input_text", "text": "Research how to connect an MCP server to an OpenAI agent, check for recent updates, and summarize the recommended setup." } ] } ] }' For a runtime comparison, see the Agents overview . The Agents API retains session state so you can continue work across turns without
rebuilding the conversation context. You can delete sessions and published
artifacts when you no longer need them.
The Agents API currently supports data residency only in the United States and
does not support Zero Data Retention (ZDR). Choosing a self-hosted sandbox does
not make the Agents API ZDR-eligible. See Data controls
in the OpenAI platform for details on data residency and retention.
aquir350185
🟧 hnOpenAI Agents APIushakov130
🟧 echo.blog ⭐OpenAI introduces the Agents API; the accompanying documentation and Reddit account describe managed Codex orchestration with durable sessioOpenAI——
🟧 hnOpenAI Agents API, here we go, the assistant API again?ltononro20
🟧 openaiIntroducing the Agents API
Retrieved article excerpt

Open article · Retrieved 2026-09-12T00:21:26.268642+00:00

September 10, 2026

[Product](https://openai.com/news/product-releases/)[API](https://openai.com/stories/api/)

# Introducing the Agents API

Build and run cloud agents with the Codex harness, fully managed by OpenAI.

Loading…

Share

As we’ve scaled Codex and ChatGPT for Work to millions of people around the world, we’ve learned what it takes to make long-running agents work well in practice. Useful agents need a powerful harness that manages context, uses tools efficiently, and coordinates subagents. They also need infrastructure that keeps them running reliably for days, with environments where they can work with files, run code, and save intermediate results.

Today, we’re introducing the [Agents API⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/agents-api/overview) in public beta, bringing that same harness and infrastructure that powers Codex to developers through a simple, flexible API.

## What our customers are saying about Agents API

1 of 8

> “With the Agents API, our evaluation score went from 0.71 to 0.85. The subagent support in the API is great and drastically sped up our workflow. Previously it was pretty cumbersome to observe and orchestrate subagents in our old setup but the new APIs gave us a 4x latency reduction. We spent a long time trying to optimize for this and the subagent flows were a huge out-of-the-box lift.”

Jack Weissenberger, CTO, Ciridae

> “Transforming real-world businesses means deploying AI into workflows of every shape. Agents API supplies the harness; the environment, context, and UX stay ours. With our AI platform Nexus we now stand up agents in hours across industries, from residential services to architecture.”

Rasmus Wissmann, CTO, Long Lake

> “The Agents API has enabled us to think differently about how we can architect complex, multi-step workflows. We used to write prompt chains and manage our own set of tool calls, but now we can use agents directly in our code much like how Codex works on your laptop. It’s already helped us solve several problems that would’ve otherwise required us to build custom agent infrastructure.”

Cole Striler, Director of Engineering, WithCoverage

> “After migrating our case review workflow to the Agents API, we saw a 60% reduction in cost per case, lower latency, and significantly improved token efficiency while maintaining existing performance.”

Bhavyansh Sabharwal, Member of Technical Staff, SafetyKit

> “What stood out in our testing was how naturally the Agents API handled bursty workloads. We could fan out work across hundreds of agents, run them asynchronously, and collect the results later, without keeping infrastructure idle between peaks.”

Dmitry Khanukov, Co-founder & CTO, Dwelly

> “Earning customers’ trust is critical in financial services. OpenAI’s Agents API enables us to build more reliable agents, giving customers the confidence to use them in production. By separating the agent harness from the sandbox, we reduced failed agent responses by 86%.”

Serhii Shchoholiev, Lead Engineer, Hypha

> “The Agents API handled the implementation, independent review, remediation, and real-browser validation in a real, active repository. Overall, the agent’s engineering quality was very strong.”

Maks Operlejn, Senior ML Engineer, deepsense.ai

> “At Nash, we deploy thousands of long-running AI agents that manage hundreds of millions of deliveries across global logistics networks. OpenAI’s Agents API gives us the durable session and orchestration layer we need for agents operating continuously in production managing context, recovery, and multi-step execution, while Nash provides the tools and execution environment that connect them to the physical world. This lets our agents reason, act, recover, and collaborate across complex workflows that can span hours or days. These agents are production infrastructure running mission-critical logistics operations for our partners.”

Aziz Alghunaim, Co-founder & CTO, Nash.ai

- Ciridae
- Long Lake
- WithCoverage
- SafetyKit
- Dwelly
- Hypha
- deepsense.ai
- Nash.ai

## Build cloud agents with a single API call

With the Agents API, you can create a production-ready agent in a single API call by specifying the task, model, tools, and environment:

#### JavaScript

```` ```
1

import OpenAI from "openai";



2



3

const client = new OpenAI();



4



5

const session = await client.beta.agents.sessions.create({



6

agent: {



7

model: "gpt-6-astra",



8

tools: [



9

{



10

type: "mcp",



11

server_label: "observability",



12

transport: {



13

type: "http",



14

server_url: "https://observability.example.com/mcp",



15

},



16

},



17

],



18

multi_agent: { enabled: true, max_concurrent_subagents: 3 },



19

},



20

vault_ids: ["vault_YOUR_VAULT_ID"],



21

environment: {



22

type: "openai_hosted",



23

capability_directories: ["/workspace/capabilities/skills"],



24

},



25

input:



26

"Investigate service-api’s elevated 5xx rate over the last 30 minutes. " +



27

"Delegate deployment, error, and dependency analysis to subagents. " +



28

"Save findings, evidence, and recommended mitigation in /workspace/outputs.",



29

});
``` ````

OpenAI hosts and maintains the harness. You choose the agent’s compute environment: in an OpenAI-managed sandbox, on your own infrastructure, or with one of our sandbox partners. The Agents API gives you a strong foundation for building agents on top of our optimized agent harness and infrastructure, so you can focus on the tools, knowledge, and workflows that make your agent unique.

An application sends tasks to the Agents API and receives events and output. The Agents API runs the managed Codex harness, sending tool calls to a sandbox and receiving tool results. The application controls self-hosted compute.

Agents API powers your agents with the same harness and infrastructure behind Codex.

## Choose your agent environment

Different workloads need different compute, storage, and deployment options. The Agents API lets you choose a sandbox that fits your application.

We’re [partnering with ecosystem providers⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/agents-api/environments/self-hosted#sandbox-providers), including Blaxel, Cloudflare, Daytona, DigitalOcean, E2B, Modal, Oracle, Runloop, and Vercel, to provide first-class integrations for a range of needs:

- Fully managed environments or deployments within your VPC
- Specific file and secret storage mechanisms
- Different CPU, GPU, and memory configurations, with performance, cold-start, and cost profiles to match your company’s workflow.

Sandbox partners: Modal, Cloudflare, Daytona, Blaxel, Runloop, Vercel, Oracle, E2B, and DigitalOcean.

The Agents API offers first-class integrations with popular ecosystem providers.

## OpenAI hosted sandboxes

For developers who want to get started quickly and scale efficiently, we’re also introducing the [OpenAI hosted sandbox⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/agents-api/environments/openai-hosted). This leverages the same sandboxing infrastructure that powers Codex and ChatGPT.

OpenAI provisions and manages the sandbox, giving your agent a secure and performant environment to run code, work with files, and produce artifacts. These sandboxes can be flexibly configured with your files, packages, skills and plugins to give the agent what it needs to complete the task.

## Build with an evolving Codex harness

Taking advantage of new model capabilities often means reworking your harness, taking valuable time away from improving your application. The Agents API provides versioned access to these capabilities with each model launch. We maintain and continuously improve the harness alongside our models, helping your agents get better performance from every upgrade. For example, recent improvements to the harness include:

### Keep agents working across long sessions

To support models working for hours, we’ve built context management that helps agents carry relevant information across longer sessions. The Agents API [automatically compacts⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/compaction) earlier context as a session approaches its context limit, preserving information the agent needs to continue. Developers can build workflows that span multiple context windows without implementing their own compaction logic.

### Help agents efficiently use more tools

The Agents API helps agents find the right tools and use them efficiently. [Tool search⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/tools-tool-search) loads relevant tool definitions as needed, helping reduce token usage and cost while preserving the model’s cache. Once tools are available, [programmatic tool calling⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/tools-programmatic-tool-calling) lets agents run calls in parallel, chain related operations, and filter or combine results in code so they can work through large volumes of data while bringing only the relevant results back into context. The Agents API supports MCP, custom functions, and built-in tools like web search.

#### JSON

```` ```
1

"agent": {



2

"tools": [



3

{



4

"type": "mcp",



5

"server_label": "openai_docs",



6

"transport": {



7

"type": "http",



8

"server_url": "https://developers.openai.com/mcp"



9

}



10

},



11

]



12

}
``` ````

### Let agents parallelize work with subagents

With [multi-agent support⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/agents-api/multi-agent), the Agents API can break complex tasks into independent pieces and delegate them to subagents that work in parallel. Each subagent maintains its own context, helping it stay focused on its assignment, while the main agent coordinates their work and brings the results together. This can speed up research, analysis, and coding tasks that benefit from parallel work, without requiring you to build your own orchestration.

#### JSON

```` ```
1

"agent": {



2

"model": "gpt-6-astra",



3

"multi_agent": {



4

"enabled": true,



5

"max_concurrent_subagents": 3,



6

}



7

}
``` ````

## An open-source foundation

The Agents API is powered by the open-source Codex harness, giving developers visibility into the core logic that coordinates model calls, tools, and context. With the Agents API, OpenAI operates and maintains that harness while developers can inspect and learn from its [public codebase⁠(opens in a new window)](https://github.com/openai/codex).

## Start building

Agents API is available in public beta today to all developers. There are no additional fees for using the Agents API – you simply pay for the tokens and tools your agents use, as outlined on our [pricing page⁠(opens in a new window)](https://developers.openai.com/api/docs/pricing).

Explore the [Agents API overview⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/agents-api/overview) to learn more, or follow the [quickstart⁠(opens in a new window)](https://developers.openai.com/api/docs/guides/agents-api/quickstart) to get started and bring the harness behind Codex into your own agents.

During the public beta, we’ll iterate quickly based on your feedback as we work toward general availability. Let us know what’s working, where you’re running into friction, and what you need to build and run your agents in production.

- [API](https://openai.com/news/?tags=api)
- [Codex](https://openai.com/news/?tags=codex)
- [2026](https://openai.com/news/?tags=2026)

## Author

OpenAI

## Keep reading

[View all](https://openai.com/news/)

Now everyone can put data to work — card image

[Now everyone can put data to work

ProductSep 10, 2026](https://openai.com/index/put-data-to-work/)

FinServ Blog - Art Card Texture Square

[Introducing ChatGPT for Financial Services

ProductSep 10
OpenAI——
🟠 redditWeek in review: OpenAI ships managed Agents API, Apple's new Siri reportedly runs on Gemini, and three vendors add agent spend controls
artificial
ksraj100110
🟠 redditBe careful with the new Agents API, I just paid $1600 for idle containers
OpenAI
Wide-Arugula304214939
🟠 redditOpenAI is preparing a new Codex Cloud with Tailscale and Azure workload identity
OpenAI
ryanmerket7210
🟧 hnComputer Use in the Agents APIacossta10
🟧 hnOpenAI – Codex gets reusable cloud envs that work across devicessrnvs20

Interpretation history

Decision trace