skyvern.com agentic web readiness

A Manifest validity: 67% (2/3 valid, 3 errors, 7 warnings) · Surface score 46 (coverage 30 + breadth 6 + conformance 10). 4 standards observed across 3 of 9 steps; 3 manifests present (+ robots.txt), 3 errors, 7 warnings. Checked 2026-10-25 03:18:12 UTC via www.skyvern.com. This grades the agent-facing files published at skyvern.com, not the organisation's products.

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

Coverage by step

Manifests

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

What an agent can call

• MCP endpoint https://api.skyvern.com/mcp (streamable-http) — from /.well-known/mcp.json
• API description https://api.skyvern.com/openapi.json (application/openapi+json)
• API description https://www.skyvern.com/docs/api-reference (text/html)
• API description https://api.skyvern.com/.well-known/oauth-authorization-server (application/json)
• API description https://www.skyvern.com/.well-known/mcp.json (application/json)
• llms.txt: Skyvern, 26 links
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed
• OAuth protected resource https://api.skyvern.com/mcp, authorization servers: https://api.skyvern.com

Standards observed

• llms.txt https://skyvern.com/llms.txt
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://skyvern.com/.well-known/api-catalog
• OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://skyvern.com/.well-known/oauth-protected-resource
• Markdown for Agents https://skyvern.com/

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": "skyvern.com"}))
2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for skyvern.com

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

3. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
   Generate starter /.well-known/security.txt for skyvern.com

   Contact: mailto:security@skyvern.com
   Expires: 2027-09-20T18:30:39Z
   Canonical: https://skyvern.com/.well-known/security.txt
   Preferred-Languages: en
   Policy: https://skyvern.com/security-policy
   

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://api.skyvern.com/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://api.skyvern.com/mcp 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 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 28/35, conformance 10/15, total 88/100, grade A+.

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