prisma.io agentic web readiness

B Manifest validity: 67% (2/3 valid, 2 errors, 12 warnings) · Surface score 33 (coverage 20 + breadth 3 + conformance 10). 3 standards observed across 2 of 9 steps; 3 manifests present (+ robots.txt, security.txt), 2 errors, 12 warnings. Checked 2026-10-25 03:17:09 UTC via www.prisma.io. This grades the agent-facing files published at prisma.io, not the organisation's products.

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

Coverage by step

Manifests

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

What an agent can call

• MCP endpoint https://mcp.prisma.io/mcp (http) — from /.well-known/mcp.json
• MCP endpoint https://mcp.prisma.io/mcp (http), tools: fetch_workspace_details, list_prisma_postgres_databases, create_prisma_postgres_database, delete_prisma_postgres_database, list_prisma_postgres_connection_strings, create_prisma_postgres_connection_string, delete_prisma_postgres_connection_string, list_prisma_postgres_backups, create_prisma_postgres_recovery, introspect_database_schema, execute_sql_query, execute_prisma_postgres_schema_update, list_object_store_buckets, create_object_store_bucket, delete_object_store_bucket, create_object_store_bucket_key, delete_object_store_bucket_key, search_prisma_documentation, list_prisma_compute_apps, list_prisma_compute_builds — from /.well-known/mcp/server-card.json
• llms.txt: Prisma Website, 172 links, llms-full.txt present
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)

Standards observed

• llms.txt https://prisma.io/llms.txt
• Agent Skills https://prisma.io/.well-known/agent-skills/index.json
• Markdown for Agents https://prisma.io/

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

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

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": "prisma.io"}))

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback agent_skills). Call the MCP endpoint at https://mcp.prisma.io/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://mcp.prisma.io/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 19/20, readability 30/30, capabilities 23/35, conformance 10/15, total 82/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