Reading the site as markdown
Every page on infrawrench.com is available as markdown, for agents and anything else that would rather not parse HTML.
The website answers in markdown as well as HTML. This is for readers that aren’t browsers — AI agents, scripts, terminal tools — and it needs no API key.
Three ways to get it
Ask for it. Send an Accept header that prefers markdown:
curl -H 'Accept: text/markdown' https://infrawrench.com/
Append .md. Every page has a markdown twin at the same path:
curl https://infrawrench.com/index.md
curl https://infrawrench.com/docs/features/agent-auth.md
Start from the index. /llms.txt lists every markdown URL on the site, grouped by section, with a one-line description each:
curl https://infrawrench.com/llms.txt
robots.txt points at it too, so a crawler that starts where crawlers start will find it.
What counts as asking for markdown
Negotiation covers the home page and every documentation page — both render on demand, so both see your Accept header.
Markdown wins when you weight it above HTML:
curl -H 'Accept: text/markdown;q=1.0, text/html;q=0.1' https://infrawrench.com/
It also wins when you name it first and give no weights at all, which is how most HTTP clients express a preference:
curl -H 'Accept: text/markdown, text/html, */*' https://infrawrench.com/
q decides first; where markdown and HTML carry the same weight, the one named first wins. text/plain and text/x-markdown both count as markdown.
A request with no preference gets HTML. That includes Accept: */*, which is what most browsers and plain curl send — asking for “anything” isn’t asking for markdown, and treating it as such would serve plain text to the entire web. Browsers never name markdown at all, so they never negotiate into it.
Every page advertises its markdown twin two ways, for clients that would rather follow a link than set a header — a response header:
Link: <https://infrawrench.com/index.md>; rel="alternate"; type="text/markdown"
and a tag in the HTML head:
<link rel="alternate" type="text/markdown" href="/docs/features/agent-auth.md" />
The negotiated responses carry Vary: Accept, so a shared cache keeps the two representations apart rather than serving whichever it saw first.
If you’re an agent
The markdown home page leads with how to register for a trial workspace without a human involved. See agent authentication for the full story, or fetch app.infrawrench.com/auth.md for instructions written for you rather than about you.
See also
- Agent authentication — registering, and the claim ceremony
- MCP server — the tool-calling endpoint