whereby.com agentic web readiness

D Manifest validity: 0 manifests published (0 errors, 4 warnings) · Surface score 10 (coverage 10 + breadth 0 + conformance 0). 1 standard observed across 1 of 9 steps; 0 manifests present, 0 errors, 4 warnings. Checked 2026-10-25 23:43:15 UTC. This grades the agent-facing files published at whereby.com, not the organisation's products.

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

Coverage by step

Manifests

What an agent can call

• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)

Standards observed

• Markdown for Agents https://whereby.com/

Cheapest next steps

1. llms.txt: one Markdown index file; the most widely read agent-facing file
   Generate starter /llms.txt for whereby.com

   # Whereby
   
   > Whereby and what it offers to agents
   
   Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.
   
   ## Docs
   - [Getting started](https://whereby.com/docs/getting-started): the first page to read
   - [API reference](https://whereby.com/openapi.json): OpenAPI description
   
   ## Optional
   - [Changelog](https://whereby.com/changelog): what changed, newest first
   

2. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "whereby.com"}))
3. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for whereby.com

   # Whereby for agents
   
   Whereby and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://whereby.com/llms.txt
   - API description: https://whereby.com/openapi.json
   - Discovery catalog: https://whereby.com/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://whereby.com/mcp
   - Rate limits and authentication: describe them here
   
   ## Conventions
   - How to cite or attribute content
   - What not to do (no scraping of /account/, no automated sign-ups, etc.)
   
   Contact: security@whereby.com
   

Agent pre-flight & practical readiness

Preferred mode: markdown_negotiation. GET / with Accept: text/markdown. The origin already serves a Markdown body for agents. whereby.com publishes no root agent discovery manifests, but docs.whereby.com serves /llms.txt (138 links). Probe docs.whereby.com or publish /.well-known/ard.json on whereby.com to link them.

Fetch: GET https://whereby.com/ GET / with Accept: text/markdown. The origin negotiates a Markdown body.

Subdomain discovery hint (subdomain_stranded): whereby.com publishes no root agent discovery manifests, but docs.whereby.com serves /llms.txt (138 links). Probe docs.whereby.com or publish /.well-known/ard.json on whereby.com to link them. (check docs.whereby.com)

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 30/30, capabilities 2/35, conformance 0/15, total 52/100, grade B.

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). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. 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