infisical.com agentic web readiness

B Manifest validity: 75% (3/4 valid, 1 error, 7 warnings) · Surface score 39 (coverage 20 + breadth 9 + conformance 10). 5 standards observed across 2 of 9 steps; 4 manifests present (+ robots.txt, security.txt), 1 error, 7 warnings. Checked 2026-10-25 18:32:32 UTC. This grades the agent-facing files published at infisical.com, not the organisation's products.

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

Coverage by step

Manifests

{
  "specVersion": "1.0",
  "host": {
    "displayName": "Infisical",
    "identifier": "did:web:infisical.com",
    "documentationUrl": "https://infisical.com/AGENTS.md"
  },
  "entries": [
    {
      "identifier": "urn:air:infisical.com:mcp:infisical",
      "displayName": "Infisical MCP server",
      "type": "application/mcp-server-card+json",
      "url": "https://infisical.com/mcp/server-card",
      "description": "Infisical and what it offers to agents. Streamable HTTP MCP server.",
      "representativeQueries": [
        "what can the Infisical MCP server do",
        "use Infisical tools from an agent"
      ],
      "tags": [
        "mcp",
        "mcp-server"
      ]
    },
    {
      "identifier": "urn:air:infisical.com:api:openapi",
      "displayName": "Infisical API description",
      "type": "application/openapi+json",
      "url": "https://infisical.com/openapi.json",
      "description": "OpenAPI description of the Infisical API.",
      "representativeQueries": [
        "Infisical API reference"
      ],
      "tags": [
        "openapi",
        "api"
      ]
    }
  ]
}

What an agent can call

• API description https://infisical.com/openapi.json (application/vnd.oai.openapi+json;version=3.0)
• API description https://infisical.com/openapi.json (application/vnd.oai.openapi+json)
• API description https://infisical.com/docs/api-reference (text/html)
• llms.txt: Infisical, 17 links, llms-full.txt present
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed; Agentmap https://infisical.com/.well-known/ard.json
• ARD bridge (/.well-known/ard.json): 3/19 valid, 0 legacy, 0 dead/broken

Standards observed

• llms.txt https://infisical.com/llms.txt
• Agentic Resource Discovery https://infisical.com/.well-known/ard.json
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://infisical.com/.well-known/api-catalog
• Markdown for Agents https://infisical.com/
• MCP Server Cards (SEP-2127)

Cheapest next steps

1. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for infisical.com

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

Agent pre-flight & practical readiness

Preferred mode: openapi (fallback llms_txt). Read the published API description and call those operations. Scraping HTML skips the interface the site already gave you.

Fetch: GET https://infisical.com/openapi.json GET the API description and call the documented operations.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0, HTML-to-llms.txt token ratio 2.982×.

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 14/35, conformance 10/15, total 74/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