proof.com agentic web readiness

A+ Score 60 (coverage 30 + breadth 15 + conformance 15). 8 standards observed across 3 of 9 steps; 5 manifests present, 0 errors, 5 warnings. Checked 2026-10-20 05:31:29 UTC via www.proof.com. This grades the agent-facing files published at proof.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/proof.com.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

What an agent can call

• API description https://dev.proof.com/openapi/proof-business-api-specification.json (application/openapi+json)
• API description https://dev.proof.com/docs/business-quick-start (text/html)
• API description https://dev.proof.com/openapi/proof-real-estate-api-specification.json (application/openapi+json)
• API description https://dev.proof.com/docs/real-estate-quick-start (text/html)
• API description https://dev.proof.com/openapi/verifiable-credentials-api.json (application/openapi+json)
• API description https://dev.proof.com/docs/digital-credentials-overview (text/html)
• API description https://dev.proof.com/openapi/oauth-api.json (application/openapi+json)
• API description https://dev.proof.com/reference/authorizeoauth (text/html)
• API description https://dev.proof.com/openapi/proof-scim-api-specification.json (application/openapi+json)
• API description https://dev.proof.com/reference/createuser (text/html)
• API description https://dev.proof.com/openapi/proof-logs-api-specification.json (application/openapi+json)
• API description https://dev.proof.com/reference/listsecurityevents (text/html)
• API description https://dev.proof.com/openapi/organization-certificates-openapi-specification.json (application/openapi+json)
• API description https://dev.proof.com/openapi (text/html)
• llms.txt: Proof for AI agents, 0 links
• robots.txt AI policy: unlisted crawlers allowed
• OAuth protected resource https://api.proof.com, authorization servers: https://api.proof.com

Standards observed

• llms.txt https://proof.com/llms.txt
• Content Signals Policy https://proof.com/robots.txt
• Agentic Resource Discovery https://proof.com/.well-known/ard.json
• AI Catalog well-known file https://proof.com/.well-known/ai-catalog.json
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://proof.com/.well-known/api-catalog
• OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://proof.com/.well-known/oauth-protected-resource
• OAuth Client ID Metadata Document https://proof.com/.well-known/oauth-authorization-server
• AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

1. AGENTS.md: instructions for coding agents working on or with the site
2. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
3. MCP Server Cards (SEP-2127): if you run an MCP server, a SEP-2127 card at <mcp-url>/server-card lets clients configure themselves

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules