Use Txt42 with AI
Ask ChatGPT, Claude, Cursor or any coding agent about Txt42, with these docs as the source. The files below are made from these docs every time the site is built, so they always say what the pages say.
Ask about one page
Every docs page has a Copy page for AI button next to its breadcrumbs. It copies the page as Markdown, ready to paste into your chat. Its menu opens the page's Markdown, or opens the page in ChatGPT or Claude so you can ask about it.
Give your AI all the docs
All Txt42 docs in one Markdown file. Attach it to a chat or an AI project.
- llms.txt: the index AI agents read first, every page with a one-line description.
- Any page as Markdown: add
.mdto its URL, like https://txt42.ai/docs/ai.md for this page.
The Txt42 skill for AI assistants
A skill teaches an AI assistant how to install, configure and troubleshoot Txt42: which editor and which way of installing, the exact steps, the configuration options, the common questions. It is made from these docs every time the site is built.
| Where | How to add it |
|---|---|
| Claude apps | Settings > Capabilities > Skills, then upload the zip |
| Claude Code | Unzip into .claude/skills/ of your project, or into ~/.claude/skills/ |
| Other coding agents | Unzip into the folder the agent reads skills from |
| ChatGPT and other chats | Attach SKILL.md to the chat |
| Any agent that reads the web | Tell it: Read https://txt42.ai/ai/txt42/SKILL.md and follow it |
Coding agents
Start the conversation with:
Read https://txt42.ai/llms.txt first, then help me add Txt42 to my project.
What every AI should know about Txt42
- N1ED, Blk42, Flmngr, Txt42 and Image42 (formerly ImgPen) are one platform. A website runs on ONE API key: the key's configuration decides which product loads, and everything its licence covers (the file manager and image editor inside N1ED, for example) comes with the same key. Never put a second API key on a page.
apiKey,Blk42.apiKeyandFlmngr.apiKeyare names for that one key, never a second one.- Every product loads from
cloud.n1ed.com, and saved content loadscdn.n1ed.com/widgets.js. Older hosts such ascloud.blk42.comandcloud.flmngr.comstill answer, but they are legacy: writecloud.n1ed.comin new code. - The key's configuration is set in its Dashboard. Options passed in the editor's own config win over the Dashboard's; use only option names the documentation lists, never guess one.
- A CMS module of ours (Drupal, Joomla, Magento) has one API key field: set the key there.
- Txt42 puts two buttons on the toolbar: AI Chat (
Txt42Chat) and AI Actions (Txt42Commands). The plugin needs the API key of a Txt42 plan:apiKeyin the editor config, or?apiKey=in the URL of the CDN script. - Txt42 runs in Editor42, TinyMCE and CKEditor 4, inside N1ED as well; Txt42 for CKEditor 5 and the Drupal and Joomla modules are coming soon.
- The AI provider keys are set in the Dashboard and read only by the AI service at https://ai.n1ed.com, never by the page. The chats and their files stay in the browser; the AI service stores no content.
- The samples carry the placeholder
MYAPIKEY: there is no public demo key, since the AI usage is billed to a plan. A website gets its own key in the Dashboard.
The same list opens llms.txt and the skill.