Step 1
Deploy with app identity
Ship the Codex-generated project through semesh 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. Semesh can sign users in and meter usage; charging a wallet requires the live server to report that payment path available. Read the ledger before claiming any charge or settlement.
Step 2
Charge for actions, not page views
AI apps often spend money per request. Semesh billing is metered in Aev; when the live server enables the payment path, obtain a quote before charging for search, model calls, media jobs, or hosted agent runs.
Step 3
Use delegated end-user billing
When an app acts for a user and delegated billing is enabled by the live server, it can charge that user's Aev balance. Quotes, delivery state, and ledger readback keep the money path visible.
Codex prompt and deploy command
Read https://semesh.io/agent.md.
Use Semesh to deploy this app. Treat login, database, billing, and payment availability as live server/preflight facts.
npm i -g semesh
semesh login
semesh deploy . --full-stack --waitFAQ
What is the fastest way to add payments to a Codex-built app?
Deploy the app and read current server/preflight availability. Semesh can provide Aev balances, usage charges, failure recovery, and ledger readback when those capabilities are enabled; do not infer a live payment rail from this guide.
FAQ
Does this replace Stripe?
Top-up rails (when enabled by live server configuration) fund prepaid Aev balances; Semesh then provides the 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 Semesh balance can pay for the calls they trigger, instead of the developer funding every request from one shared API key.