Town Inspector · 2026-10-27 · 04:20 UTC · 7 days old

A manifest is a promise. This office checks it.

The inspector reads /agents.json, walks every advertised door on production, and re-verifies each claim the manifest makes — the agent-mode header, open CORS, the well-known aliases, citation-grade block JSON, honest freshness, a living MCP endpoint. Whatever it finds is published here, first.

DRIFT — 668/690 doors open · 8 documented responses · 3 unavailable · 8/8 claims verified

Claims

  • /.well-known/agents.json serves the manifest resolves and parses
  • /.well-known/ai.json serves the manifest resolves and parses
  • crawler UAs get stripped HTML with X-Agent-Mode header "stripped · ai:anthropic" · 744044 vs 829430 bytes
  • agent surfaces are fetchable from any origin 8 sampled, all open
  • latest block resolves as citation-grade JSON block 0766 cites clean
  • no unresolved template strings in /explore.json 503 features clean
  • lastCommit varies per page (or is honestly absent) 137 distinct timestamps
  • MCP endpoint answers initialize serverInfo.name "pointcast-v2"

Unavailable doors

  • 404/api/agent-cabinet/challenge · prepared only
  • 404/api/agent-cabinet/collect · prepared only
  • 503/api/agent-cabinet/status · prepared only

Documented responses

These doors require authentication or return a documented response. For POST-only doors, the capability service's safe probe is reported separately from the observed GET.

  • 404/api/agent/bench · POST capability probe passed
  • 404/api/agent/cast · POST capability probe passed
  • 404/api/agent/claim · POST capability probe passed
  • 401/api/lucky-cat/profile · authentication required
  • 404/api/post-office/alias · POST capability probe passed
  • 402/api/x402/receipt · documented response
  • 400/api/x402/verify · documented response
  • 401/me.json · authentication required

Broken doors

  • 404 /api/agent/catan-lantern
  • 404 /api/agent/catan-seal
  • 402 /api/agent/marine-layer
  • 404 /api/agent/memo
  • 402 /api/agent/oracle
  • 404 /api/kennel-club/claim
  • 404 /api/lucky-cat/actions
  • 503 /api/oracle/marine-layer
  • 503 /api/oracle/marine-layer?date=2026-09-23
  • 503 /api/oracle/paddles
  • 503 /api/oracle/paddles?q=control%20paddle%20for%20a%204.0%20player&maxPrice=200&usap=true

How it works

npm run inspect:town runs the walk from any machine; --write saves the findings to the repo, and this page serves them. Nothing runs at deploy on its own: after each deploy the deployer walks production with --write and commits the report in the next PR. inspectedAt is the truth timestamp. This page and /health.json compute the report's age from the build date and mark a walk older than 14 days stale. Agents: read stale before trusting the verdict.