agenticweb.wiki

docs.jina.ai agentic web readiness

C Manifest validity: 18% (2/11 valid, 12 errors, 10 warnings) · Surface score 23 (coverage 20 + breadth 3 + conformance 0). 3 standards observed across 2 of 9 steps; 11 manifests present (+ security.txt), 12 errors, 10 warnings. Checked 2026-10-26 09:29:20 UTC. This grades the agent-facing files published at docs.jina.ai, not the organisation's products.

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

Coverage by step

01 Discoveragents.txt02 Identifynothing observed03 Permitnothing observed04 Readllms.txt, AGENTS.md05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
errors
  • body is not valid JSON
View valid /.well-known/ard.json template for docs.jina.ai
{
  "specVersion": "1.0",
  "host": {
    "displayName": "Docs",
    "identifier": "did:web:docs.jina.ai",
    "documentationUrl": "https://docs.jina.ai/AGENTS.md"
  },
  "entries": [
    {
      "identifier": "urn:air:docs.jina.ai:mcp:docs",
      "displayName": "Docs MCP server",
      "type": "application/mcp-server-card+json",
      "url": "https://docs.jina.ai/mcp/server-card",
      "description": "Docs and what it offers to agents. Streamable HTTP MCP server.",
      "representativeQueries": [
        "what can the Docs MCP server do",
        "use Docs tools from an agent"
      ],
      "tags": [
        "mcp",
        "mcp-server"
      ]
    },
    {
      "identifier": "urn:air:docs.jina.ai:api:openapi",
      "displayName": "Docs API description",
      "type": "application/openapi+json",
      "url": "https://docs.jina.ai/openapi.json",
      "description": "OpenAPI description of the Docs API.",
      "representativeQueries": [
        "Docs API reference"
      ],
      "tags": [
        "openapi",
        "api"
      ]
    }
  ]
}
AI Catalog well-known file
/.well-known/ai-catalog.json
errors
  • body is not valid JSON
View valid /.well-known/ai-catalog.json template for docs.jina.ai
{
  "specVersion": "1.0",
  "host": {
    "displayName": "Docs",
    "identifier": "did:web:docs.jina.ai",
    "documentationUrl": "https://docs.jina.ai/AGENTS.md"
  },
  "entries": [
    {
      "identifier": "urn:air:docs.jina.ai:mcp:docs",
      "displayName": "Docs MCP server",
      "type": "application/mcp-server-card+json",
      "url": "https://docs.jina.ai/mcp/server-card",
      "description": "Docs and what it offers to agents. Streamable HTTP MCP server.",
      "representativeQueries": [
        "what can the Docs MCP server do",
        "use Docs tools from an agent"
      ],
      "tags": [
        "mcp",
        "mcp-server"
      ]
    },
    {
      "identifier": "urn:air:docs.jina.ai:api:openapi",
      "displayName": "Docs API description",
      "type": "application/openapi+json",
      "url": "https://docs.jina.ai/openapi.json",
      "description": "OpenAPI description of the Docs API.",
      "representativeQueries": [
        "Docs API reference"
      ],
      "tags": [
        "openapi",
        "api"
      ]
    }
  ]
}
MCP Server Cards (SEP-2127)
/mcp/server-card
errors
  • body is not valid JSON
View valid /mcp/server-card template for docs.jina.ai
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "ai.jina.docs/docs",
  "title": "Docs",
  "version": "1.0.0",
  "description": "Docs and what it offers to agents",
  "websiteUrl": "https://docs.jina.ai/",
  "icons": [
    {
      "src": "https://docs.jina.ai/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://docs.jina.ai/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json
errors
  • body is not valid JSON
View valid /.well-known/agent-card.json template for docs.jina.ai
{
  "name": "Docs",
  "description": "Docs and what it offers to agents",
  "version": "1.0.0",
  "provider": {
    "organization": "Docs",
    "url": "https://docs.jina.ai/"
  },
  "documentationUrl": "https://docs.jina.ai/AGENTS.md",
  "supportedInterfaces": [
    {
      "url": "https://docs.jina.ai/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    }
  ],
  "url": "https://docs.jina.ai/a2a",
  "protocolVersion": "1.0",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "defaultInputModes": [
    "text/plain"
  ],
  "defaultOutputModes": [
    "text/plain"
  ],
  "skills": [
    {
      "id": "answer",
      "name": "Answer questions",
      "description": "Answer questions about Docs.",
      "tags": [
        "qa"
      ],
      "examples": [
        "What does Docs do?"
      ]
    }
  ],
  "securitySchemes": {},
  "securityRequirements": []
}
llms.txt
/llms.txt
valid
  • the H1 is not the first line
  • no blockquote summary under the title
  • no Markdown links: list the pages an agent should read
AGENTS.md
/AGENTS.md
valid
Agent Skills
/.well-known/agent-skills/index.json
errors
  • body is not valid JSON
View valid /.well-known/agent-skills/index.json template for docs.jina.ai
{
  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
  "skills": [
    {
      "name": "docs",
      "type": "skill-md",
      "description": "Docs and what it offers to agents",
      "url": "https://docs.jina.ai/.well-known/agent-skills/docs/SKILL.md",
      "digest": "sha256:0000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog
errors
  • body is not valid JSON
View valid /.well-known/api-catalog template for docs.jina.ai
{
  "linkset": [
    {
      "anchor": "https://docs.jina.ai/",
      "service-desc": [
        {
          "href": "https://docs.jina.ai/openapi.json",
          "type": "application/openapi+json"
        }
      ],
      "service-doc": [
        {
          "href": "https://docs.jina.ai/docs/api",
          "type": "text/html"
        }
      ],
      "service-meta": [
        {
          "href": "https://docs.jina.ai/AGENTS.md",
          "type": "text/markdown"
        }
      ]
    }
  ]
}
AI Crawler User-Agent Tokens in robots.txt
/robots.txt
errors
  • no User-agent group at all
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (unspecified)
  • no Sitemap: line
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
  • no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
View valid /robots.txt template for docs.jina.ai
# search and answer-engine crawlers
User-agent: Googlebot
User-agent: bingbot
User-agent: OAI-SearchBot
User-agent: Claude-SearchBot
User-agent: PerplexityBot
User-agent: ExaSearchBot
User-agent: TavilyBot
Allow: /

# model-training crawlers: choose Allow or Disallow and keep it explicit
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
User-agent: meta-externalagent
User-agent: Bytespider
Disallow: /

# user-triggered fetchers (a person asked for this page)
User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Perplexity-User
Allow: /

# default fallback for unlisted crawlers (RFC 9309 §2.2.1: specific groups above take precedence over *)
User-agent: *
Allow: /
Disallow: /account/
Content-Signal: ai-train=no, search=yes, ai-input=yes

Sitemap: https://docs.jina.ai/sitemap.xml
Agentmap: https://docs.jina.ai/.well-known/ard.json
security.txt (RFC 9116)
/.well-known/security.txt
errors
  • Contact: missing (RFC 9116 requires it)
  • Expires: missing (RFC 9116 requires it)
  • Canonical: missing
View valid /.well-known/security.txt template for docs.jina.ai
Contact: mailto:security@docs.jina.ai
Expires: 2027-09-21T18:22:05Z
Canonical: https://docs.jina.ai/.well-known/security.txt
Preferred-Languages: en
Policy: https://docs.jina.ai/security-policy
auth.md
/auth.md
errors
  • none of the auth.md mechanism names found (identity_assertion, service_auth, anonymous)
View valid /auth.md template for docs.jina.ai
# Authenticating to Docs as an agent

This file is the agent-auth skill for docs.jina.ai. It is linked from the authorization server's metadata (`agent_auth.skill`).

## Discovery
1. Call the API. A `401` carries `WWW-Authenticate: Bearer resource_metadata="https://docs.jina.ai/.well-known/oauth-protected-resource"`.
2. Read `/.well-known/oauth-protected-resource` (RFC 9728) for `resource` and `authorization_servers`.
3. Read the authorization server's `/.well-known/oauth-authorization-server` (RFC 8414); the `agent_auth` block lists the endpoints below.

## Methods we accept
- `identity_assertion`: you hold a session for a user and can mint an ID-JAG with `aud` = our `resource`. Preferred.
- `service_auth`: you only know the user's email. A claim ceremony (6-digit code) is required.
- `anonymous`: no user. Immediate limited scopes; the user can claim later.

## Register
POST `agent_auth.identity_endpoint` with `{"type": "<method>", ...}`; exchange the returned `identity_assertion` at the token endpoint for an access token.

## Scopes
- `api.read`: read
- `api.write`: write (claimed registrations only)

## Rules
- Show the user our name and the scopes before asserting their identity.
- Keep `claim_token` in memory only.
- Revocation events arrive as Security Event Tokens at your registered events endpoint.
Open Knowledge Format
/okf/index.md
errors
  • missing YAML frontmatter block (--- ... ---)
  • missing okf_version (0.1 or 0.2) in frontmatter (OKF §8)
  • no Markdown links to concept .md files
View valid /okf/index.md template for docs.jina.ai
---
okf_version: "0.2"
title: "Docs Knowledge Bundle"
description: "Docs and what it offers to agents"
---

# Docs Knowledge Bundle

> Docs and what it offers to agents

- [Update Log](log.md)

## Concepts

- [Docs Overview](concepts/docs.md) — Docs and what it offers to agents

What an agent can call

Standards observed

Cheapest next steps

No cheap file is missing, or the origin never answered.

Agent pre-flight & practical readiness

Preferred mode: llms_txt. GET /llms.txt and follow the links it names. That index is the page list an agent should read.

Fetch: GET https://docs.jina.ai/llms.txt GET /llms.txt and follow its links.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high.

AI crawler posture: all_ai_blocked · Assistant access: OpenAI unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.

Readiness subscores: reach 0/20, readability 20/30, capabilities 4/35, conformance 0/15, total 24/100, grade D.

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