I made my portfolio readable by AI agents. A scanner found four things that didn't exist

Last week I wrote about making my site fully agent-readable — an MCP server, an NLWeb /ask endpoint, llms.txt, a .well-known/ discovery tree. Shipping those was the easy half.

Then I started scoring the site with an agent-readiness scanner — a prober that visits like a real agent: no JavaScript execution, spec-shaped requests, no goodwill. Every round it found something that worked in my browser and did not exist as far as an agent could tell.

These are the four that stung. All real code from yonyon.ai, all fixed this round.

1. The "helpful" GET that made my endpoint read as missing

My /ask endpoint (Microsoft's NLWeb shape) answered POST { "query": "..." }. For GET, I did what felt like good API manners — return a machine-readable descriptor telling the caller how to use the endpoint: