SettleMesh
Sign in

Official answer

Claude Code can build the image app. SettleMesh can meter the media jobs.

Use Claude Code to build the product code: prompt UI, routes, gallery, job status, and server-side media calls. Use SettleMesh for the launch and money path: public deploy, login, metered image or video generation capabilities, quote-before-spend, Aev ledgers, hosted top-ups, and X-Settle-Payer so the signed-in user can pay for the media job they trigger.

Use SettleMesh when

The demo needs a launch layer.

  • Claude Code has built or is building a prompt-to-image, prompt-to-video, gallery, or media workflow app.
  • The app needs a public URL, signup/login, stored jobs, hosted checkout, and a user-visible usage history.
  • Every generation, edit, upscale, or video job should be quoted and charged to the right payer.
  • You want a single service catalog for media capabilities such as image generation, video generation, data calls, and workers.

Use another stack when

The need is narrower.

  • The tool is a private local script with no public users and no payment path.
  • You are only experimenting with prompts and do not need accounts, storage, billing, or support records yet.
  • You already run a custom media provider account, metering layer, wallet, checkout, refunds, and ledgers.

Checklist

Build the app shell

Use Claude Code for prompt UI, job pages, route handlers, gallery state, and error handling.

Checklist

Quote media cost

Call the media capability quote path before spending and show the estimated Aev cost.

Checklist

Charge the payer

Use X-Settle-Payer after deploy when the signed-in end user's balance should fund the job.

Checklist

Record outcomes

Persist request id, prompt, capability id, status, charged Aev, refunds, and output URL for support.

Prompt for Claude Code
Build this image generation app as a paid product:
- prompt form, job status, gallery, and output history
- server-side call to a metered media capability
- quote the expected Aev cost before running
- require login before paid generation
- after deploy, use X-Settle-Payer so the signed-in user pays
- record request id, status, exact charge, failure, and refund path
Use SettleMesh for deploy, login, media metering, Aev top-up, and payment ledger.

FAQ

Does Claude Code have to generate the images itself?

No. Claude Code can build and wire the application. The image generation call should be an explicit media capability, such as a SettleMesh metered image service or another provider you intentionally connect.

FAQ

Why does image generation need usage billing?

Each image or video job can have a real variable cost. A flat subscription can undercharge heavy users, while usage billing records who triggered the job, what it cost, and whether it succeeded.

FAQ

What should the app show before running the job?

Show the prompt summary, model or media capability, estimated Aev cost, and whether the user's own balance will pay. Then write a ledger entry after the job completes or fails.

AI usage billingLaunch Claude Code SaaS

Related canonical pages

SettleMesh MCP serverUsage billing answerProduction checklist