Credits in your published app: who pays for AI usage

The workspace that owns your app pays for its built-in AI usage. Visitors' ChatGPT, Claude or Overskill accounts do not pay that bill.

What uses credits

Each built-in AI request uses credits: chatbot replies, summaries, generated images and other AI features. Charges are per request, not per visit. Model choice and measured usage affect the amount.

Check credit history after a small test and monitor usage after launch. Buyer credits can give customers an allowance at your markup, but your workspace still covers the underlying cost.

Use your own provider

There is no switch that moves built-in AI to your own provider account. To build a separate integration:

1. Open Dashboard → Env Vars and save your provider key under a name such as MY_OPENAI_API_KEY. Names such as OPENAI_API_KEY are reserved.
2. Ask the builder to create a server endpoint using that key and connect the feature to it.
3. Test the feature and check which account was billed.

Calls through your own provider are billed by that provider. Keep the key on the server.

Let visitors use their own AI tool manually

Your app can assemble a prompt from a template, let the visitor copy it into their own AI tool, then accept the pasted result. Assembling text with ordinary code does not call AI.

Any built-in AI calls used to create or check that text still use your workspace's credits. Do not collect visitors' chat passwords or session cookies. An automatic per-user provider connection needs its own supported authentication and billing design.

See What uses credits and Out of credits.