Working with an AI tool¶
These guides are published so that a coding agent or a chat assistant can read them as easily as you can. Everything below is served from this site, and needs no account and no key.
The markdown source of any page¶
Every page is served twice: as HTML for reading, and as markdown at the same path with .md on the end. The markdown is the source these pages are written in, so an assistant reading it gets the commands and the checklists without the navigation and styling wrapped around them.
curl https://guides.edgible.com/capabilities.md
curl https://guides.edgible.com/guides/n8n-on-edgible/03-n8n-public-webhook-hostname.md
At the top of each page there are two actions next to the edit pencil. One copies that page's markdown to your clipboard, ready to paste into a chat. The other opens the markdown in the browser.
The whole site in one fetch¶
llms.txt is an index. It lists every page as a link to its raw markdown, each with a one-line summary, so an agent can pick what it needs rather than crawling the site.
curl https://guides.edgible.com/llms.txt
llms-full.txt is every page concatenated into a single document, for a tool that would rather take the corpus in one go than fetch pages individually. curl -sI https://guides.edgible.com/llms-full.txt gives you its size before you fetch it.
curl https://guides.edgible.com/llms-full.txt
Terms in one place¶
Glossary defines every term the guides use, so an assistant can pick up the vocabulary in one fetch rather than inferring it chapter by chapter:
curl https://guides.edgible.com/glossary.md
For evaluators and architects is a short positioning page for readers who already know tunnels and self-hosting ingress. It uses the same vocabulary without product comparisons or pricing:
curl https://guides.edgible.com/appendix/for-evaluators.md
The tunneling dream scores Edgible against the four requirements in the awesome-tunneling dream list, including the one that is not met:
curl https://guides.edgible.com/appendix/the-dream.md
Ways people use this¶
Point an assistant at llms.txt and ask which chapter covers what you are trying to do. The summaries are written to make that question answerable without opening every page.
Paste a single chapter into a chat and work through it with the assistant watching the output. Each chapter states what you should have when you finish and ends with a checklist, so an assistant has something concrete to compare your terminal output against.
Give a coding agent the markdown for a chapter and have it adapt the commands to your machine names, ports and organisation, rather than you editing each command by hand.
Ask a question against the whole corpus by fetching llms-full.txt, when you do not yet know which guide the answer is in.
The cards live in edgible-org/cards. The catalog at cards.edgible.org lists them with their test results, and its llms.txt indexes every card and need for an assistant. The format, the schema, and the tools live in edgible-org/card-kit. card.schema.json is the source of truth for a card. The card README is how you fetch a card, edit card.env, start the containers, and publish. card-image.py draws the picture. An assistant that can run edgible reads that schema and the cards in the repo. Self Hosting is Social is the idea. The guide does not keep a second copy of those files.
curl https://raw.githubusercontent.com/edgible-org/card-kit/main/card.schema.json
curl https://raw.githubusercontent.com/edgible-org/card-kit/main/card-image.py
curl https://raw.githubusercontent.com/edgible-org/cards/main/website/README.md
curl https://raw.githubusercontent.com/edgible-org/cards/main/website/card.yml
curl https://guides.edgible.com/guides/self-hosting-is-social/README.md
How current a page is¶
Every page carries the date its source last changed: at the foot of the HTML, and in the first two lines of the markdown, alongside the page's canonical URL.
Source: https://guides.edgible.com/guides/n8n-on-edgible/01-n8n-on-the-vm.md
Last updated: 2026-08-28
Those two lines travel with the text when it is pasted into a chat, which is what lets an assistant cite the page and lets you work out later which version you followed. The date comes from the commit history of the repository, not from a field anyone maintains by hand. A page dated some months ago is not necessarily wrong, but it is worth checking a version number or a command flag against the tool you are running.
Crawling¶
robots.txt allows everything, for search engines and answer engines alike. This is public documentation, and being quoted accurately is the point. sitemap.xml lists every page.
What to keep an eye on¶
An assistant that has read these guides will happily produce commands for your machines. The guides publish services and change what is reachable from the public internet, so read a command before you run it, particularly anything that creates an app with None auth or changes what a service binds to.
Assistants also blend sources. If an answer mentions an Edgible flag or a command that does not appear in any chapter here, treat it as invented until you have seen it in the CLI itself.