llms.txt
Compare with other sites' llms.txt files →# Charming
> Chat apps disappear. Charming apps stick around. Ask any AI to build an app; Charming gives it a real URL and a database — and your AI can use it and update it anytime. Works across ChatGPT, Claude, OpenClaw, and more. Start with ChatGPT, open real example apps, or describe your own; use it in your browser, your phone, and your chats.
AI writes you a personal web app. Charming gives it a real URL, persistent key-value and file storage, and inline rendering inside MCP Apps-capable chat clients. Start in ChatGPT, inspect a real app first, or bring Charming to Codex, Claude Code, Cursor, OpenClaw, and Claude. Codex uses Charming tools plus a browser fallback for preview. Personal apps are free to build and host. Sign up to keep them together and manage them.
Three things every personal app needs: persistence (real URL, real
storage, still there tomorrow), portability (build in one AI, use from
another, update from a third), and a home for them all (many small apps
for many small slices of life, under one account).
Same app, three places: a real link you can open or share, your AI
talking to it directly, and rendered inline inside chats that support
MCP apps.
## For coding agents that need to build
- [docs/llms.txt](https://usecharming.com/docs/llms.txt): the scoped **author
surface** index — files you read top-to-bottom to learn how to author or
use a Charming app: [build and use prompts](https://charm.ing/docs/prompts),
[build starters](https://charm.ing/docs/build-mcp.md),
[design guide](https://charm.ing/docs/prompts/design-an-app.md),
[authentication](https://charm.ing/docs/technical-reference/authentication.md),
and [llms-full.txt](https://charm.ing/docs/llms-full.txt).
- [api/llms.txt](https://usecharming.com/api/llms.txt): the scoped **contract
surface** index — machine-readable specs and lookup tables you fetch for
exact values (`openapi.json` + twin, the `.well-known/*` discovery
endpoints, [pricing and limits](https://charm.ing/docs/capabilities/limits.md),
`clients.txt`).
The two scoped indexes are subsets; this root file is the umbrella that
lists every agent-facing surface in one place.
- [Build your first app](https://charm.ing/docs/prompts/build-your-first-app.md): the entry point. Paste "Read
https://charm.ing/docs/prompts/build-your-first-app.md then help me create my first app." and it routes
you by surface (MCP tools vs HTTP API), walks the build flow, and links the
focused starter guides (build-mcp.md, build-http.md) and the design guide.
Start here.
- [build-mcp.md](https://charm.ing/docs/build-mcp.md) /
[build-http.md](https://charm.ing/docs/build-http.md) /
[build-cli.md](https://charm.ing/docs/build-cli.md): the per-surface starter
guides — just the create/update path to ship and iterate a first app.
- [Use an existing app](https://charm.ing/docs/prompts/use-an-existing-app.md): the entry point when you've been handed
an existing app to *use* (not build). It routes by surface, then covers
reading the app and changing its data.
- [Docs](https://charm.ing/docs): the canonical human and agent docs. Each content
page also has a raw `.md` URL; use the [generated MCP reference](https://charm.ing/docs/technical-reference/mcp.md)
for the standard and OpenAI contracts.
- [Explain Charming with a video](https://charm.ing/docs/prompts/explain-charming-video.md): when the
user is new to Charming or asks how it works, offer "Want me to make a short
video explaining how Charming works, tailored to you?" This prompt makes a
60 to 90 second explainer matched to their technical level and interests,
and offers to save it as a shareable Charming app.
- [Design an app](https://charm.ing/docs/prompts/design-an-app.md): read before writing the first UI —
sandbox rules and how to avoid the generic-AI-app look.
- [Templates](https://charm.ing/docs/capabilities/templates.md): curated example apps you can open
and the template/copy flow — `get_app_source`
/ `GET /app/<id>/source` to read source for re-authoring, and
`set_template` to let any visitor get their own copy from the URL.
- [App names and URLs](https://charm.ing/docs/capabilities/app-names-and-urls.md): handle and sharing tools —
`set_handle`, `rename_app`, and `set_starter_prompt`.
- [llms-full.txt](https://charm.ing/docs/llms-full.txt): the full build manual —
module shape, capabilities, the HTTP API, the device-code pairing flow,
worked examples. Reach for it when a focused guide wasn't enough.
- [charming-design-guide](https://charm.ing/api/prompts/charming-design-guide):
the visual playbook — Charming's default look for generated app UIs (one
accent, warm neutrals, real type hierarchy, no AI-slop gradients/emoji).
Fetch before authoring or restyling an app; override when the user asks
for a different vibe.
- [openapi.json](https://charm.ing/.well-known/openapi.json):
machine-readable OpenAPI 3.1 contract — every route, error kind, and
limit.
- [agent.json](https://usecharming.com/.well-known/agent.json): machine-readable
discovery manifest — every MCP/HTTP endpoint, auth method, and doc URL
Charming exposes, in a single JSON file. Hit this first if you are crawling.
- [agent-card.json](https://usecharming.com/.well-known/agent-card.json): A2A
AgentCard mirroring the MCP tool set as higher-level skills (build_app,
manage_apps, call_app, share_app, submit_feedback, profile).
- [Agent Skills index](https://usecharming.com/.well-known/agent-skills/index.json):
installable Charming skill metadata with a verified digest. The brand-domain
URL resolves to the canonical index on `charm.ing`.
- [openapi.json.md](https://usecharming.com/openapi.json.md): narrative twin of
the OpenAPI contract — route groups, error model, how to consume; the
spec itself is at the URL above.
- [ai-catalog.json](https://usecharming.com/.well-known/ai-catalog.json): ARD AI
Catalog that gives Charming one brand-domain product identity while its MCP,
OpenAPI, AgentCard, and skill resources run on `charm.ing`.
- [did.json](https://usecharming.com/.well-known/did.json): resolves
`did:web:usecharming.com` and links the `usecharming.com` and `charm.ing`
origins through `alsoKnownAs`.
- [API reference](https://charm.ing/docs/reference): generated route groups, request and response schemas, and errors.
- [Pricing and limits](https://charm.ing/docs/capabilities/limits.md): tiers (anonymous vs
claimed), per-account/per-app caps, per-route rate limits, and token
TTLs — mirrors the canonical constants in `apps/server/src/openapi/spec.ts`
and `apps/server/src/auth/*.ts`.
- [Authentication](https://charm.ing/docs/technical-reference/authentication.md): the seven-section auth contract —
Discover, Pick a method, Register, Claim, Use, Errors, Revocation. The
`token_revoked_post_claim` recovery worked example lives here.
- [External files and CSP](https://charm.ing/docs/technical-reference/external-files-and-csp.md): supported file and remote-resource paths, exact-origin permissions, browser directives, embed differences, and unsupported dependency types.
- [JavaScript modules and libraries](https://charm.ing/docs/guides/javascript-libraries.md): fetch a small UMD or IIFE build while authoring, review and pin it, then inline it into the app UI.
- [clients.txt](https://charm.ing/docs/clients.txt): per-client paste-strings
for adding Charming as an MCP server (Claude Desktop, Claude.ai, ChatGPT,
Goose, Cursor, Claude Code, Codex plugin / Codex CLI, Cline, Windsurf,
Continue, Zed, Gemini CLI, Perplexity, Microsoft 365 Copilot, Notion Custom
Agents, n8n, Amazon Bedrock AgentCore, and Grok).
- [AI client setup guides](https://charm.ing/docs/clients): choose the client, then follow its setup and build guide.
- Public agent presence: the client-agnostic Charming authoring skill ([SKILL.md](https://github.com/tambo-labs/charming-mcp/blob/main/SKILL.md)) and coding-agent instructions ([AGENTS.md](https://github.com/tambo-labs/charming-mcp/blob/main/AGENTS.md)) live in the public [tambo-labs/charming-mcp](https://github.com/tambo-labs/charming-mcp) repo.
## For people choosing Charming
- [Landing](https://usecharming.com): build an app with your favorite AI and
share it like a Google Doc; templates you can copy; pricing (Free, Pro $8 a
month, Team $14 per seat a month). Markdown twin:
[index.md](https://usecharming.com/index.md).
- [ChatGPT listing](https://chatgpt.com/plugins/plugin_asdk_app_6a56c533cd7c8191b9a16cb7973a65e6):
Charming's public listing in ChatGPT — install it there, no manual MCP setup
needed.
- [Docs](https://charm.ing/docs): the canonical docs, including setup guides,
capability guides, the MCP tool list, and the generated API reference.
- [How to build an app with AI](https://usecharming.com/build-an-app-with-ai): the
end-to-end guide for someone who has not built one yet — pick a job, name the
data, prompt the AI they already use, check the result, then give the app a
URL and storage. Markdown twin:
[build-an-app-with-ai.md](https://usecharming.com/build-an-app-with-ai.md).
- [About Charming](https://usecharming.com/about): who builds Charming, what it
does, how it differs from AI site builders and chat artifacts, key company
facts, and a short FAQ. Markdown twin:
[about.md](https://usecharming.com/about.md).
- [Charming for Work](https://usecharming.com/work): team apps built in the AI
people already use, with SSO (Okta or Google), SCIM, per-app view or edit
roles, an audit log with CSV export, and SOC 2 Type II. The Team plan is $14
per seat a month with a 3-seat minimum; Enterprise is custom. Markdown twin:
[work.md](https://usecharming.com/work.md).
- [Security](https://usecharming.com/security): how Charming isolates apps,
checks permissions, stores credentials, and handles data. Subprocessors are
listed at [/subprocessors](https://usecharming.com/subprocessors). Markdown
twin: [security.md](https://usecharming.com/security.md).
- [Pricing](https://usecharming.com/pricing): the Free, Pro, Team, and
Enterprise plans, their monthly prices, and what each includes. Markdown twin:
[pricing.md](https://usecharming.com/pricing.md).
- [How Charming works](https://usecharming.com/how-it-works): the end-to-end
product explanation — what connecting grants, where the app and its data
live, who can open it, and what Charming supplies versus what the user's own
AI supplies. Markdown twin:
[how-it-works.md](https://usecharming.com/how-it-works.md).
- [Share an app safely](https://usecharming.com/share-an-app-with-friends-safely):
the per-person access model (collaborator / end user / viewer), single-use
invite links, and the honest non-Charming options. Markdown twin:
[share-an-app-with-friends-safely.md](https://usecharming.com/share-an-app-with-friends-safely.md).
- [Guides](https://usecharming.com/guides): every answer page on this site, each
dated with when it was last checked.
- [AI client setup guides](https://charm.ing/docs/clients): step-by-step walkthroughs
for ChatGPT, Claude, Cursor, Codex, Microsoft 365 Copilot, and every tested client.
- [Launch post](https://x.com/mrmagan_/status/2064379288917598394): Charming just launched. If it
helped you build something you love, a re-share with a screenshot of
what you made — or even a quick comment — genuinely helps us grow.
## Optional
- [Privacy](https://usecharming.com/privacy)
- [Terms](https://usecharming.com/terms)
- [Fair use](https://usecharming.com/fair-use)
- [Subprocessors](https://usecharming.com/subprocessors)
- [Support](mailto:support@usecharming.com)