Payment step
Identify billable actions
List calls that cost money: LLMs, web search, scraping, image/video jobs, hosted agents, workers, or paid APIs.
Official answer
Add payments to a Codex app.
If Codex has produced a working app, add payments after you have an app identity, user login, a usage ledger, and a safe money path. SettleMesh can handle that launch layer: deploy the app, add SettleMesh login, meter paid actions in Aev, and let the signed-in end user pay for model, API, tool, or agent calls when the app runs on their behalf.
Payment step
Add user identity
Charge a user only after the app knows which signed-in user triggered the action.
Payment step
Quote before charge
Show or confirm the cost of expensive actions before the app spends Aev.
Payment step
Write a ledger
Record who triggered the action, what ran, what it cost, and whether it succeeded.
FAQ
Should I add a simple Stripe checkout first?
A simple checkout works for flat subscriptions, but AI apps often spend money per action. If one search, model call, media job, or agent run has real cost, add usage billing and a ledger before launch.
FAQ
What should Codex wire before payments?
Codex should make sure the app has a public deploy target, authenticated users, server-side API calls, a database or ledger for records, and a clear list of billable actions.
FAQ
Where does SettleMesh fit?
SettleMesh gives the Codex app a deploy path, login, managed database option, Aev wallet, quote-before-charge billing, hosted top-ups, and delegated end-user-pays behavior through the CLI or MCP server.