featkpr

For the thing reading this without eyes

The map, as an answer

A map is a better answer to “what does this product do?” than a rendered page is. So we serve it as one.

Markdown mirrors Intended

Every page answers Accept: text/markdown, and each has a .md twin, so an agent reads the text and not the chrome.

A read-only MCP server Intended

Two tools over the public demo maps, both readOnlyHint. No key, no write path, nothing of yours in it.

llms.txt and a routing card Intended

Under a kilobyte, saying what lives where — so a crawler spends one request instead of forty.

None of this is live yet, and the labels above say so. When a piece ships, its label changes here on the same day — we would rather be dull than be caught.

Want this on your product?

We are building the first version with a handful of teams. Tell us what you test with and what breaks.