Biggest gap: Public pricing page.
Core 58/60, plus the average of sign-up (24/40) and API (35/40). Scanned 3 Nov 2026.
Latest live check, 11 Nov 2026
93Agent readiness / 100
Agent-readyScored for: Get an API key
Core58/60
Get an API key35/40
What an agent gets measured, not scored
7 of 7AI agents that get the real page
≈6.0kTokens to read the homepage
0.1 sHomepage load for an agent
Same pageAgents see what browsers see
Agent by agent (7 of 7 get in)
- INClaude-User sent by a person200
- INChatGPT-User sent by a person200
- INPerplexity-User sent by a person200
- INOAI-SearchBot answer engine200
- INPerplexityBot answer engine200
- INGPTBot training crawler200
- INClaudeBot training crawler200
We send each agent's name from our own servers. A site that checks IP addresses may treat the real agent differently.
Fix these first
- +5 OAuth client self-registration. Support dynamic client registration (RFC 7591) so MCP clients connect in one click.
- +2 Dates show the content is fresh. Show published and updated dates (and dateModified in JSON-LD). Put "as of" dates on key facts like pricing.
All 22 checks
- PASSAgents get the real page, not a bot wall12
- PASSrobots.txt lets user-triggered agents in6
- PASSAnswer-engine crawlers are allowed4
- PASSContent is in the raw HTML6
- PASSSemantic HTML (main, nav, header)4
- PASSIcon buttons and links have names3
- PASSForm fields have labels3
- PASSImages have alt text3
- PASSThe page has an H12
- PASSStructured data (JSON-LD)5
- PASSMeta description and Open Graph tags3
- PASSsitemap.xml3
- PASSllms.txt4
- FAILDates show the content is fresh2
- PASSOpenAPI spec7
- PASSRemote MCP server8
- PASSDocs as markdown5
- PASSSelf-serve API keys6
- FAILOAuth client self-registration5
- PASSOAuth discovery metadata3
- PASSSDKs and a CLI3
- PASSFree tier or test keys3
Newer standards (8/9, not scored yet)
- YESMarkdown for agents Return markdown when an agent sends Accept: text/markdown. Fewer tokens, cleaner answers. How–
- YESContent Signals in robots.txt Say what AI may do with your content (search, ai-input, ai-train), separately from crawling. How–
- YESAgent Skills index Publish /.well-known/agent-skills/index.json so agents can find skills for using your product. How–
- YESAPI catalog (RFC 9727) Publish /.well-known/api-catalog listing your API specs, so agents find them without guessing. How–
- YESLink headers to machine-readable versions A Link header on the homepage pointing at your API description, docs or markdown version. How–
- YESWebMCP tools on the page Register your page's actions as tools (navigator.modelContext) so browser agents call them instead of guessing at buttons. How–
- NOauth.md for agent sign-up Publish /auth.md saying how an agent registers and gets credentials for a user. How–
- YESAI Catalog Publish /.well-known/ai-catalog.json listing your MCP servers and agents, so clients find them from the domain alone. How–
- YESMissing pages return 404 A made-up URL should return 404, not 200. Agents treat a 200 as a real page and quote it. How–
Full checklist for boldsign.comReport page and badgeShare: X / LinkedIn /
How to fix these gaps
Add the badge to your README or site
[](https://agentsready.dev/c/boldsign.com)