agenticweb.wiki

kraken.com agentic web readiness

C Manifest validity: 50% (1/2 valid, 3 errors, 8 warnings) · Surface score 20 (coverage 10 + breadth 0 + conformance 10). 1 standard observed across 1 of 9 steps; 2 manifests present (+ robots.txt, security.txt), 3 errors, 8 warnings. Checked 2026-10-25 03:14:32 UTC via www.kraken.com. This grades the agent-facing files published at kraken.com, not the organisation's products.

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

Coverage by step

01 DiscoverRFC 972702 Identifynothing observed03 Permitnothing observed04 Readnothing observed05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json
absent HTTP 404
MCP Server Cards (SEP-2127)
/.well-known/mcp.json
errors
  • $schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json)
  • name missing
  • description missing
  • 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[]
  • remotes missing: a card with no remotes gives clients nothing to connect to
  • no ETag
View valid /mcp/server-card template for kraken.com
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "com.kraken/kraken",
  "title": "Kraken",
  "version": "1.0.0",
  "description": "Kraken and what it offers to agents",
  "websiteUrl": "https://kraken.com/",
  "icons": [
    {
      "src": "https://kraken.com/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://kraken.com/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json
absent HTTP 404
llms.txt
/llms.txt
absent HTTP 404
AGENTS.md
/AGENTS.md
absent HTTP 404
Agent Skills
/.well-known/agent-skills/index.json
absent HTTP 404
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
no AI tokens
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial)
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
  • no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
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. llms.txt: one Markdown index file; the most widely read agent-facing file
    Generate starter /llms.txt for kraken.com
    # Kraken
    
    > Kraken and what it offers to agents
    
    Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.
    
    ## Docs
    - [Getting started](https://kraken.com/docs/getting-started): the first page to read
    - [API reference](https://kraken.com/openapi.json): OpenAPI description
    
    ## Optional
    - [Changelog](https://kraken.com/changelog): what changed, newest first
    
  2. 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": "kraken.com"}))
  3. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for kraken.com
    # Kraken for agents
    
    Kraken and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://kraken.com/llms.txt
    - API description: https://kraken.com/openapi.json
    - Discovery catalog: https://kraken.com/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://kraken.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@kraken.com
    

Agent pre-flight & practical readiness

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

Fetch: GET https://mintlify-s3-bucket-3cc1a52.s3.us-east-1.amazonaws.com/fabc1f26-5178-435c-93ea-4f7e9e7fe022?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=ASIAULUIU2DM… GET the API description and call the documented operations.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 114583 (~112 KB of head/script markup before main text), JSON-LD Organization, FinancialService, Person, ImageObject, ContactPoint, PostalAddress, Certification, Service, WebSite, BreadcrumbList, ListItem, WebPage.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 19/20, readability 22/30, capabilities 8/35, conformance 10/15, total 59/100, grade B.

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