Markdown for AgentsServe AI agents Markdown instead of HTML.
An AI agent gets the same HTML a browser does: navigation, scripts, styles and tracking. Switch this on and nsin converts eligible pages to clean Markdown at the edge when an agent asks for it. People still get the normal page.
Standard content negotiation
An agent sends Accept: text/markdown and gets Markdown back. Nothing changes on your server and nothing changes for browsers. The response says how many tokens the Markdown costs and how many the HTML would have.
- Typically 5–10× fewer tokens
- X-Markdown-Tokens and X-Original-Tokens headers
- Vary: Accept, so caches keep both versions apart
Never breaks a working page
If a response is not a 200 HTML page, is too large, or cannot be parsed in time, nsin serves the original untouched. The request still shows in your logs with the reason.
- Falls back to HTML instead of failing
- Images, JSON and redirects pass through as they are
- A hot page converts once, then is reused
A tester that shows the saving
Give the tester a hostname and a path. It fetches the URL as a browser and as an agent and shows the status, whether it converted, the token count of each and the percentage saved.
- Before and after token counts
- Live view of negotiated, converted and fallback requests
- One switch per domain, off by default
Frequently asked questions
Do my visitors see Markdown?
No. Only a client that asks for text/markdown gets Markdown. Browsers always get your HTML.
Do I need to change my site?
No. The conversion happens at the nsin edge. You switch it on under AI Crawl Control, in the Optimization tab.
Why does it matter how many tokens a page costs?
Agents pay for and are limited by tokens. A page that costs a fifth or a tenth as much is read more completely and more often.
Is it available on every plan?
It is off by default and needs an active plan on the domain.