zoom.us agentic web readiness

C Manifest validity: 50% (1/2 valid, 3 errors, 9 warnings) · Surface score 20 (coverage 10 + breadth 0 + conformance 10). 1 standard observed across 1 of 9 steps; 2 manifests present (+ robots.txt, security.txt), 3 errors, 9 warnings. Checked 2026-10-25 03:20:40 UTC. This grades the agent-facing files published at zoom.us, not the organisation's products.

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

Coverage by step

Manifests

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "us.zoom/zoom",
  "title": "Zoom",
  "version": "1.0.0",
  "description": "Zoom and what it offers to agents",
  "websiteUrl": "https://zoom.us/",
  "icons": [
    {
      "src": "https://zoom.us/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://zoom.us/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}

What an agent can call

• MCP endpoint https://mcp.zoom.us/mcp/zoom/streamable (http) — from /.well-known/mcp/server-card.json
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)

Standards observed

• Agent Skills https://zoom.us/.well-known/agent-skills/index.json

Cheapest next steps

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

   # Zoom
   
   > Zoom 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://zoom.us/docs/getting-started): the first page to read
   - [API reference](https://zoom.us/openapi.json): OpenAPI description
   
   ## Optional
   - [Changelog](https://zoom.us/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": "zoom.us"}))
3. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for zoom.us

   # Zoom for agents
   
   Zoom and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://zoom.us/llms.txt
   - API description: https://zoom.us/openapi.json
   - Discovery catalog: https://zoom.us/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://zoom.us/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@zoom.us
   

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback agent_skills). Call the MCP endpoint at https://mcp.zoom.us/mcp/zoom/streamable first. Do not scrape the HTML when a tool can answer. zoom.us publishes no root agent discovery manifests, but developers.zoom.us serves /llms.txt (283 links). Probe developers.zoom.us or publish /.well-known/ard.json on zoom.us to link them.

Fetch: POST https://mcp.zoom.us/mcp/zoom/streamable POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

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

Practical readability: exa_parsable no, markdown negotiation no, render none, HTML quality none.

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

Readiness subscores: reach 19/20, readability 0/30, capabilities 17/35, conformance 10/15, total 46/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