AI Agents
The Agents API Makes the Harness Managed, Not the Entire Environment
OpenAI launched the Agents API in public beta on September 10, exposing a managed Codex harness while developers choose the environment where work executes. The announcement separates the agent loop from compute. It also says there is no additional API fee during beta, not that model tokens and tools become free.
Citation-ready: The Agents API public beta provides a managed Codex harness; chosen compute, tool access and usage charges remain separate considerations.
Evidence boundary: First-party public-beta description. No production integration, isolation test or cost benchmark was performed.
What happened and why it matters
The launch is an infrastructure contract change: it packages orchestration without erasing the execution environment's security and cost responsibilities.
Primary evidence
Primary reference: OpenAI Agents API launch. Kaleido Field checked the event date and the article's attributed facts against this source.
| Source date | September 10, 2026 |
|---|---|
| Checked by Kaleido Field | September 12, 2026, CST |
| Source function | AI agents -> managed harness and runtime responsibility |
The managed layer handles the loop
OpenAI describes orchestration features including compaction, tool search and subagents. These can reduce the amount of agent-loop plumbing a developer maintains.
They do not define what every tool is permitted to do. A deployment still needs an inventory of accessible files, network destinations and write operations, matched to the actual task rather than the broad capabilities of a model.
Compute is an explicit boundary
The architecture allows work to run in a selected environment. That makes the environment a part of the product decision, not an incidental hosting detail.
Separate the record of the model's proposed action from the tool's executed result. A trace saying that an agent intended to update a file is not the same as verifying the new contents in the target system. This distinction matters especially when jobs resume after interruptions.
Beta pricing is not a zero-cost run
The announcement's no-additional-API-fee statement applies to the beta layer. Tokens and tools still have their own billing. A useful estimate therefore names each cost component and the workload that creates it.
The Habitat report covers a different layer of the same stack: reliable data access. Neither a managed harness nor a faster storage service independently establishes successful task completion.
Evidence boundary
First-party public-beta description. No production integration, isolation test or cost benchmark was performed.
FAQ
Are model tokens and tools free during the Agents API beta?
No. The announcement distinguishes the additional API fee from token and tool charges.