agenticweb.wiki

developers.zoom.us agentic web readiness

A Manifest validity: 67% (2/3 valid, 3 errors, 8 warnings) · Surface score 59 (coverage 40 + breadth 9 + conformance 10). 5 standards observed across 4 of 9 steps; 3 manifests present (+ robots.txt), 3 errors, 8 warnings. Checked 2026-10-25 20:26:52 UTC. This grades the agent-facing files published at developers.zoom.us, not the organisation's products.

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

Coverage by step

01 Discover02 Identifynothing observed03 PermitContent Signals Policy04 Readllms.txt05 ActAgent Skills06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json		absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json		absent HTTP 404
MCP Server Cards (SEP-2127)
/.well-known/mcp/server-card.json		errors
  • $schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json)
  • name missing
  • version missing
  • Content-Type is application/json; charset=utf-8; SEP-2127 says serve application/mcp-server-card+json
  • pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[]
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • no Access-Control-Allow-Origin: * (required for browser clients)
View valid /mcp/server-card template for developers.zoom.us
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "us.zoom.developers/developers",
  "title": "Developers",
  "version": "1.0.0",
  "description": "Developers and what it offers to agents",
  "websiteUrl": "https://developers.zoom.us/",
  "icons": [
    {
      "src": "https://developers.zoom.us/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://developers.zoom.us/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json		absent HTTP 404
llms.txt
/llms.txt		valid
  • no blockquote summary under the title
  • file is large; keep llms.txt an index and put the full text in llms-full.txt
AGENTS.md
/AGENTS.md		absent HTTP 404
Agent Skills
/.well-known/agent-skills/index.json		valid
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog		absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt
/robots.txt		no AI tokens
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (allowed)
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116)
/.well-known/security.txt		absent HTTP 404
auth.md
/auth.md		absent HTTP 404
Open Knowledge Format
/okf/index.md		absent HTTP 404

What an agent can call

Standards observed

Cheapest next steps

  1. 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": "developers.zoom.us"}))
  2. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for developers.zoom.us
    # Developers for agents

Developers and what it offers to agents

## Read the data, not the HTML
- Index: https://developers.zoom.us/llms.txt
- API description: https://developers.zoom.us/openapi.json
- Discovery catalog: https://developers.zoom.us/.well-known/ard.json

## Calling
- MCP server (Streamable HTTP): https://developers.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@developers.zoom.us
  3. api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "developers.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.

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.

Practical readability: exa_parsable yes, 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 20/20, readability 12/30, capabilities 21/35, conformance 10/15, total 63/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