agenticweb.wiki

pydantic.dev agentic web readiness

A+ Manifest validity: 71% (5/7 valid, 3 errors, 14 warnings) · Surface score 70 (coverage 50 + breadth 15 + conformance 5). 11 standards observed across 5 of 9 steps; 7 manifests present (+ security.txt), 3 errors, 14 warnings. Checked 2026-10-25 19:16:56 UTC. This grades the agent-facing files published at pydantic.dev, not the organisation's products.

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

Coverage by step

01 DiscoverARD, RFC 972702 Identifynothing observed03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, Markdown for Agents05 ActAgent Skills06 CoordinateA2A07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
errors
  • specVersion missing
  • host block missing (displayName, identifier, documentationUrl help clients name the publisher)
View valid /.well-known/ard.json template for pydantic.dev
{
  "specVersion": "1.0",
  "host": {
    "displayName": "Pydantic",
    "identifier": "did:web:pydantic.dev",
    "documentationUrl": "https://pydantic.dev/AGENTS.md"
  },
  "entries": [
    {
      "identifier": "urn:air:pydantic.dev:mcp:pydantic",
      "displayName": "Pydantic MCP server",
      "type": "application/mcp-server-card+json",
      "url": "https://pydantic.dev/mcp/server-card",
      "description": "Pydantic and what it offers to agents. Streamable HTTP MCP server.",
      "representativeQueries": [
        "what can the Pydantic MCP server do",
        "use Pydantic tools from an agent"
      ],
      "tags": [
        "mcp",
        "mcp-server"
      ]
    },
    {
      "identifier": "urn:air:pydantic.dev:api:openapi",
      "displayName": "Pydantic API description",
      "type": "application/openapi+json",
      "url": "https://pydantic.dev/openapi.json",
      "description": "OpenAPI description of the Pydantic API.",
      "representativeQueries": [
        "Pydantic API reference"
      ],
      "tags": [
        "openapi",
        "api"
      ]
    }
  ]
}
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 must be reverse-DNS with exactly one slash, e.g. com.example/weather
  • Content-Type is application/json; 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[]
  • description is over 100 characters
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key)
  • no Access-Control-Allow-Origin: * (required for browser clients)
View valid /mcp/server-card template for pydantic.dev
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "dev.pydantic/pydantic",
  "title": "Pydantic",
  "version": "1.0.0",
  "description": "Pydantic and what it offers to agents",
  "websiteUrl": "https://pydantic.dev/",
  "icons": [
    {
      "src": "https://pydantic.dev/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://pydantic.dev/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json
valid
  • supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape
  • protocolVersion is "0.3.0" (pre-1.0 legacy shape; A2A 1.0 uses protocolVersion "1.0" and supportedInterfaces[])
llms.txt
/llms.txt
valid
  • the H1 is not the first line
  • no blockquote summary under the title
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
valid
AI Crawler User-Agent Tokens in robots.txt
/robots.txt
valid
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116)
/.well-known/security.txt
valid
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. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for pydantic.dev
    # Pydantic for agents
    
    Pydantic and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://pydantic.dev/llms.txt
    - API description: https://pydantic.dev/openapi.json
    - Discovery catalog: https://pydantic.dev/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://pydantic.dev/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@pydantic.dev
    

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://logfire-us.pydantic.dev/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://logfire-us.pydantic.dev/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 35/35, conformance 5/15, total 90/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