OpenAI Codex Sites: the launch layer arrives — inside your company workspace

When the company that ships the best coding agents also ships "prompt → hosted web app," that is not a competitor showing up. That is the strongest validation yet that agents need a launch layer.

OpenAI's Codex Sites lets an agent turn a prompt into a running, hosted web app — login-gated, with a real database underneath — without you touching a deploy pipeline. That is the "deploy" half of launching an agent-built app, and OpenAI solved it cleanly, inside ChatGPT.

But launching a product is two halves. Deploy is one. Public and paid is the other — a public URL anyone can open, public signup, and a way for the people who use your app to pay for it. Codex Sites stops at the first half. It has no public links, no custom domains, and no payments at all. That second half is exactly what SettleMesh does.

What Codex Sites actually is

Codex Sites went into preview on 2026-06-02. You describe a site or app, the agent builds it, and OpenAI hosts it. Under the hood it runs on Cloudflare Workers, with D1 for the database and R2 for storage. For internal tools — a dashboard for your team, an ops console, a quick data viewer your coworkers need to log into — this is genuinely good. The friction from "agent wrote it" to "it's live and my team can use it" basically disappears. The constraint is who can reach it, and what they can do once they're there.

Availability. Codex Sites is available in ChatGPT Business and Enterprise workspaces (Business on by default; Enterprise via admin RBAC). Plus, Pro, Free, and API tiers don't have it. It's locked inside your company workspace: to use Codex Sites, and to reach what it builds, you generally have to be inside that workspace.

Sharing. A Codex Site can be shared three ways — with admins, with everyone in the workspace, or with named members. All three are scoped to your workspace. There is no "anyone with the link" public mode. That's the line between an internal tool and a product. A product is something a stranger can find, open, and use.

End-user login. Because access is workspace-scoped, the person logging in has to be a workspace member or come through your pre-configured IdP. There's no open public signup the way a normal product has.

Payments. None. Codex Sites has no payment, billing, or monetization capability of any kind. There is no path from "users use this" to "users pay for this."

The fact table (verified June 2026)

Read the table as a story, not a scorecard. OpenAI built a fast, clean path to a hosted, login-gated app for your coworkers. SettleMesh builds the path to a public, paid product for your users. Both are launch layers. They aim at different halves of "launch."

The half that's still wide open

After Codex Sites, an agent can produce a hosted app your workspace can log into. What it still can't do, by design:

• Give that app a public URL a stranger can open.


• Let that stranger sign up and log in without being added to your org.


• Charge that stranger anything — there is no payments layer to charge with.

That last one is where most agent-built apps quietly die. Your AI app burns money on every API call — charge your users for it, per use, without building billing. That's metered billing plus end-user-pays: the end user who runs the expensive call is the one who pays for it.

Here's the four-line version of the other half:

npm i -g settlemesh

settlemesh login

settlemesh deploy

# live: public app with login, a managed database, and usage billing

One command takes an agent-written app — built with any agent, Codex included — and turns it into a public product. Public URL. Public signup and login. Usage-based billing. End-user payments through hosted checkout. Aev is SettleMesh's prepaid credit unit (1 USD = 100 Aev, funded via Stripe): users top up a wallet, and every metered call quotes its cost before it runs and settles against the wallet after.

Who actually lets your AI app charge users

Codex Sites is the newest entrant, but it's not the only tool that gets you most of the way and stops short of payments. The question that matters — can the people who use your app pay you?

Where the builders offer payments at all, they hand you a Stripe integration or generate billing code, and they mean subscriptions or one-time charges. None give you usage billing — charge per call, per video, per request — as a managed layer. That's the model an AI app actually needs, because the cost an AI app incurs is per use, not per month.

This isn't a roadmap promise

The SettleMesh money paths are already running in production: discrete cost-plus markup (m between 1.0 and 1.5), the unified per-user Aev wallet, end-user-pays via the X-Settle-Payer header, nested billing, and the owner revenue split — with the end-user-pays charge flow verified on a live app. The part that's genuinely a moving target is Codex Sites itself — it's in preview.

The bigger picture

OpenAI shipping Codex Sites tells you the industry now agrees on the shape of the problem: agents build apps fast, and the bottleneck moved downstream to launching them. They solved the inside-the-workspace half. The public-and-paid half is open, and it's the half that turns an agent's output into a product with users and revenue. And it composes: today's deployed app is tomorrow's composable API — every paid app on the mesh can become a capability the next agent calls and pays for.

Try it at · github.com/StructureIntelligence. Aev is SettleMesh's prepaid credit unit: 1 USD = 100 Aev, funded via Stripe.