My life is agents now.
So my site is built for them.

Surfaces.

• Per-page Markdown source

  Every published content page has HTML and Markdown views: / pairs with /index.md; append .md to other page paths. Skip the DOM, read the prose. Review-only prototypes are not part of this publication list.

  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 current published overview: a dedicated now page if present, otherwise home). The descriptor at /.well-known/mcp.json lets MCP-aware clients auto-discover it.

  Try: /.well-known/mcp.json · API contract. 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 published content 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.

HTML stays crawlable: project descriptions and links are server-rendered, with a no-JavaScript reading fallback; no model needs to run to read them. Canonical HTML URLs are listed in sitemap.xml; each page declares its Markdown alternate and share metadata. Markdown responses also identify their preferred HTML canonical.

The homepage keeps the signature constellation and thin header/footer only, with project details behind its orbit links. Its Markdown view summarizes the reviewed public facts without adding an extra visible SEO section. Experimental local AI replies are not canonical content and are never added to Markdown or MCP responses.

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