Base44 white label setup

​

Before you start: pick your path

I can't build this from here, because I can't edit your platform's code.
Paste the message below into the AI chat of the app you want to add app
building to, such as in the Base44 editor, or into a coding agent such as
Claude Code, Cursor, or Codex, opened on your platform's project.

Set up Base44 white label in my app so my users can build apps under my brand. Use this guide: https://docs.base44.com/developers/white-label/setup/SKILL.md

• Every call to Base44’s white label API runs in a backend function, never in the app’s pages, so the token never reaches a browser.
• Don’t hold one request open for a whole build. Start the build in one call and check its progress in later calls.

​

Working rules

• The linked docs are the source of truth. Plan limits, permissions, field names, and settings live in the docs pages each step page links to. If this skill and a docs page disagree, follow the page and tell the person. If a page doesn’t load, tell the person which one and stop that step rather than guess.
• Work through the steps in order. Each step depends on the one before it. Don’t skip ahead to writing code.
• Do what you can yourself. Run commands, edit files, and check responses. Only ask the person for what needs their account, their decision, or their secret.
• Verify before you continue. Every step ends with a check. If it fails, use the next action listed for that failure, or the troubleshooting page, not a guess.
• Say when it’s not on them. When a check fails for a reason the person can’t fix, such as a platform limit or something you’ll handle yourself, say clearly that they don’t need to do anything.
• Keep secrets out of the conversation. Never ask the person to paste a token or key into chat, and never print one in your output, logs, or commits. If they paste one anyway, tell them to delete it and create a new one, and don’t use the pasted one.
• Stay on task. Don’t suggest unrelated changes to the person’s app while the setup is in progress.
• Say what you deferred. When you leave something out to keep a build simple, or because the plan doesn’t include it, tell the person what it is and where it’s documented.

​

Steps

• 1. Collect the keys. Get the workspace ID, save the personal access token as a secret, and confirm the token works. Read keys.
• 2. Brand the agent. Turn on white label, and set the brand and agent names, the design system, and any skills. Read brand.
• 3. Build the chat. Build the app-building chat into the platform, with sign-in, app ownership, embedding, and saved conversations. Read build the chat.
• 4. Host it and set limits. Deploy or publish the integration, and queue builds so retries never charge twice. Read host and limits.
• 5. Run the acceptance test. Test it the way the person’s customers will use it, and report what passed. Read acceptance test.

Keep integration credentials out of the customer experience. Don’t add access-key forms, access-file uploads, or private-link requirements for customers unless the person chose that access model. Tokens and keys belong in setup and server configuration only.