Give your Lovable or Replit app an optional user-funded AI route

A Lovable or Replit project can look ready to share while its AI funding still belongs to the person who built it. The screens work, the database saves records, and one developer-controlled provider account sits behind every request.

Adding AI Pass gives users another way to fund those requests: connect a wallet through OAuth instead of supplying a provider key or relying on your account. This is an application integration you implement in the generated project. It is not a claim of a native Lovable or Replit partnership, built-in billing switch, or automatic compatibility with every generated app.

Use a concrete example: a workshop planner that turns an instructor's outline into an agenda and participant handout. The useful outcome is a printable session pack, not another general chat window.

Inspect what the generator already built

Ask the coding tool to identify the current AI call before requesting changes. Where does the prompt live? Which screen invokes it? Does the request leave the browser directly, or pass through a backend function? Who pays today? Does the application deduct its own credits?

Also locate the instructor's saved workshops and account permissions. A generated application may spread this logic across components and service wrappers. If the tool changes only the button while leaving an old automatic request in place, one click could activate both funding routes.

The first deliverable should be a short map of the existing path. Require filenames and actual behavior from the repository, not a generic diagram based on the framework name.

Give the builder a product-sized change

A useful prompt is specific about what must remain:

Add "Pay per use with AI Pass" to the workshop draft action. Keep the existing provider option and default unchanged. Preserve login, saved workshops, current hosting, and plan permissions. Use the official AI Pass integration skill and select the browser or backend path after inspecting the current request. Do not add a second generation call, move the app to another host, or invent SDK methods. Show the proposed files and acceptance checks before implementation.

Attach the official integration skill. For browser interactions, the builder should consult the SDK documentation. If the existing action depends on protected backend data, use the corresponding OAuth guidance and REST documentation.

The name of the app builder does not decide token custody. Your application architecture does.

Make the funding choice understandable

Put a compact funding selector in the generation panel. For an existing subscription product, it might offer "Use included app credits" and "Pay per use with AI Pass." If direct provider-key BYOK already exists, preserve that option too.

Do not call wallet funding "free generation." Explain what the workshop subscription buys and what the selected AI route funds. The existing billing guide explicitly separates feature permission from payment for a model call.

Let an instructor adjust session length, participant experience, and available equipment before submitting. Show those inputs in a concise review. A workshop about photography should not quietly become a lecture requiring equipment the instructor never selected.

After generation, turn the agenda into editable blocks. The instructor can shorten an exercise manually, rearrange sections, and fix an unsuitable activity without paying for a complete regeneration. If you offer "Rewrite this exercise," make its scope and funding visible as a new action.

Test the parts that a nice preview hides

Generated interfaces are especially good at looking complete. Use an acceptance sheet that describes observable behavior:

An instructor who cancels wallet connection returns to the same unsent outline. A low-balance error does not delete the workshop. Double-clicking Generate cannot create duplicate requests. Reloading the saved workshop does not regenerate its handout. The old funding option still works as designed, and an AI Pass request does not consume both wallets and app credits.

Check the published app's actual origin as well as the editor preview. Authorization that works inside a development session is not proof that the shared deployment is configured correctly. Preserve the existing deployment target; AI Pass Spaces is optional hosting, not a required migration step.

Package the instructor's work

A workshop planner has room for software revenue beyond generation: reusable activity libraries, branded participant packs, team review, and consistent exports. Choose a paid feature that remains useful after the first model response arrives.

Before charging customers, separately approve and perform a live wallet-funded verification through the deployed user flow. Until that happens, describe the integration as built or reviewed, not proven in production.

Ship the funding selector with an editable agenda and a reliable export. That is a coherent small product. A connected-wallet badge by itself is only a settings screen.