AgentGrade – agent-readiness guide for your site
Timely concept checking for /llms.txt, but it's just four HTTP GET requests.

Google for llms.txt when no dedicated crawler existed before.
AI developers and technical writers
Perplexity · Phind · Google
You can run plain queries to search across all sites:
mcp server setup vector database embeddings oauth2 refresh token
Or scope your queries to a specific site with "site: query"stripe: webhook verification mistral.ai: function calling docs.supabase.com: edge functions auth
Quotes work like Google for exact phrases:"context window limit" vector database "semantic search" stripe: "webhook signature verification"
This is still a work in progress, so looking for feedback and beta testers!- Search for humans (website): https://statespace.com/
- Search for agents (CLI, SDK, MCP, skill): https://github.com/statespace-tech/statespace
Timely concept checking for /llms.txt, but it's just four HTTP GET requests.
Evidence-mapped CV beats PDF for AI recruiter parsing, but applies only to ATS that read these formats.
Validates llms.txt and AI robot rules before AI crawlers ignore your content.
Transparent AI bot posture tracking, but 'what bots touch you' is already solved by uBlock Origin.
This is a practical playbook: the repo bundles resume.json, evidence.json, availability.json, an agent‑card and an llms.txt plus CI checks and IndexNow pushes so your CV is both human- and agent-discoverable. Clever bits: automated sitemap/index pushes, link-checking Actions, and explicit A2A‑style metadata (agent‑card.json) — that’s not something you see on most personal sites. What’s missing for wider credibility are outcome metrics and external verification (recruiter-facing analytics, attestations, or an A/B test showing improved contacts), and a clearer signal-to-noise story for what recruiters should actually consume first.
Searchable directory for llms.txt files when general search engines could index these.