AI Standards · Jesse Anderson

Surfaces.

Per-page Markdown source
Append .md to any URL and you get the source. Skip the DOM, read the prose.
Try: /about.md
/llms.txt and /llms-full.txt
A curated plaintext sitemap (Answer.AI’s convention) and a one-shot ingest of every page’s Markdown.
Try: /llms.txt · /llms-full.txt
MCP server
The site’s content is exposed as MCP tools at /api/mcp: list_pages, get_page, search, get_now. The descriptor at /.well-known/mcp.json lets MCP-aware clients auto-discover it.
Try: /.well-known/mcp.json. Or POST a JSON-RPC envelope:
```
curl -X POST https://jesselanderson.com/api/mcp \
-H 'Content-Type: application/json' \
-d '{ "jsonrpc":"2.0", "id":1, "method":"tools/list" }'
```
JSON-LD on every page
Person, Organization (Kora Labs, PapaGoose), WebSite, WebPage. Embedded in each page <head> as <script type=“application/ld+json”>.
Inspect: view source on any page and search for application/ld+json. Or fetch a page and pipe through grep -A 60 ‘ld+json’.
Page metadata
Each page exposes a title, description, slug, and content_hash (sha256 of the Markdown source). The MCP server returns those via list_pages and get_page so a client can cache and re-validate.
Try:
```
curl -X POST https://jesselanderson.com/api/mcp \
-H 'Content-Type: application/json' \
-d '{ "jsonrpc":"2.0", "id":1, "method":"tools/call", "params":{ "name":"list_pages" } }'
```
/agents.md
The agent-facing operating manual for this site. It documents the MCP endpoint, the rule about preferring the .md source over the rendered HTML, and the rate-limit posture.
Try: /agents.md
robots.txt with explicit AI directives
Allow or deny per crawler. The major AI assistants (ClaudeBot, GPTBot, PerplexityBot, OAI-SearchBot, ChatGPT-User, Google-Extended, Applebot-Extended, meta-externalagent) are allowed. Bytespider is denied.
Try: /robots.txt

Why.

I think coding is getting replaced by AI faster than the rest of the stack is catching up. I’d rather invest in standards, architecture, and machine-legibility than chase ergonomic frameworks for humans. Agents should have first-class access to what’s on this site. Engineers should be able to look at the same plumbing and decide for themselves whether I know what I’m doing.

Stack: vanilla Astro (no UI-framework integrations), a Lambda backend, no React, no TypeScript.

Surfaces.

Per-page Markdown source

/llms.txt and /llms-full.txt

MCP server

JSON-LD on every page

Page metadata

/agents.md

robots.txt with explicit AI directives

Why.