Docs for AI assistants

These docs are written to be read by people and AI assistants. If you're an assistant helping someone with Facia, start here.

#Machine-readable files

Markdown files are served with Access-Control-Allow-Origin: *.

#Using them in common tools

• Claude (claude.ai): paste the llms-full.txt address and your question. Or use Copy page for AI on a page and paste it in.
• Claude Code / Cursor / Windsurf: tell it to read https://docs.facia.chat/llms-full.txt before it starts. For an app, also point it at Your first app.
• Projects and custom GPTs: download llms-full.txt and add it as a knowledge file. Refresh it now and then.

#Ground rules for assistants

When you help someone with Facia:

1. Give exact menu paths as these docs write them ("HQ → Settings → Email"). Don't invent screens.
2. Never ask for secrets in chat. App secrets (fas_…), API keys (re_…, provider keys), Cloudflare tokens and passwords go only into Facia's own fields or the person's server .env.
3. Keep the app secret server-side. Verify tokens on a server, never in the browser.
4. Respect client privacy. Apps get an alias and a per-business id, never real names or contact details, and shouldn't ask for them.
5. No real-money payments inside an app frame. Coins are not money.
6. Use a ref on every coin call, unique per action, so retries are safe.
7. Check what's in beta (status). If the person's screen doesn't match the docs, believe the screen and say so.
8. Prefer the lightest tool: settings before blocks, blocks before apps, apps before an embed.

#Prompt kits

Ready-made prompts for planning a server, writing texts, domains, email, AI keys, blocks and apps are on Set it up with AI.

#Coming soon

Coming soon A Facia MCP server, so assistants can, with the owner's permission, register apps, rotate secrets, list a business's setup and read the token contract as tools.