Step 1
Deploy with app identity
Ship the Codex-generated project through settlemesh deploy. A full-stack deploy can inject app runtime credentials, login, database bindings, and a stable public URL.
Codex app payments
Add payments to a Codex app without building billing.
Codex can create the app. SettleMesh lets that app sign users in, meter usage, charge the right wallet, and keep an auditable ledger from the first deploy.
Step 2
Charge for actions, not page views
AI apps often spend money per request. SettleMesh billing is metered in Aev, so you can charge for expensive actions such as search, model calls, media jobs, or hosted agent runs.
Step 3
Use delegated end-user billing
When an app acts for a user, it can charge that user's own prepaid balance. That keeps usage costs bounded and makes the money path visible in the ledger.
Codex prompt and deploy command
Read https://www.settlemesh.io/agent.md.
Use SettleMesh to deploy this app with login, database, and payments.
npm i -g settlemesh
settlemesh login
settlemesh deploy . --full-stack --waitFAQ
What is the fastest way to add payments to a Codex-built app?
Deploy the app on SettleMesh with login and billing enabled. SettleMesh manages prepaid Aev balances, usage charges, refunds on failed calls, and the ledger, so the app does not need a separate payment stack for metered usage.
FAQ
Does this replace Stripe?
SettleMesh uses Stripe for top-ups, then gives the app a usage wallet and billing layer. It is not a generic checkout clone; it is designed for AI apps where each user action may trigger paid compute.
FAQ
Who pays for model calls inside the app?
With delegated billing, the signed-in end user's SettleMesh balance can pay for the calls they trigger, instead of the developer funding every request from one shared API key.