agenticweb.wiki

shadeform.ai agentic web readiness

C Manifest validity: 100% (1/1 valid, 0 errors, 3 warnings) · Surface score 20 (coverage 10 + breadth 0 + conformance 10). 2 standards observed across 1 of 9 steps; 1 manifest present, 0 errors, 3 warnings. Checked 2026-10-25 23:45:47 UTC. This grades the agent-facing files published at shadeform.ai, not the organisation's products.

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

Coverage by step

01 Discovernothing observed02 Identifynothing observed03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt04 Readnothing observed05 Actnothing observed06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
AI Catalog well-known file
/.well-known/ai-catalog.json
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
MCP Server Cards (SEP-2127)
/mcp/server-card
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
Agent2Agent Protocol
/.well-known/agent-card.json
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
llms.txt
/llms.txt
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
AGENTS.md
/AGENTS.md
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
Agent Skills
/.well-known/agent-skills/index.json
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs
/.well-known/api-catalog
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
AI Crawler User-Agent Tokens in robots.txt
/robots.txt
disallow-only
  • robots.txt names AI crawlers (GPTBot, ClaudeBot, Claude-Web, anthropic-ai, Google-Extended) only to Disallow: / — blocks AI agents rather than enabling them
  • no Sitemap: line
  • no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116)
/.well-known/security.txt
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
auth.md
/auth.md
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com
Open Knowledge Format
/okf/index.md
redirected → shadeform.com
  • not fetched: redirect off-host to shadeform.com

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 shadeform.ai
    # Shadeform
    
    > Shadeform 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://shadeform.ai/docs/getting-started): the first page to read
    - [API reference](https://shadeform.ai/openapi.json): OpenAPI description
    
    ## Optional
    - [Changelog](https://shadeform.ai/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": "shadeform.ai"}))
  3. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for shadeform.ai
    # Shadeform for agents
    
    Shadeform and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://shadeform.ai/llms.txt
    - API description: https://shadeform.ai/openapi.json
    - Discovery catalog: https://shadeform.ai/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://shadeform.ai/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@shadeform.ai
    

Agent pre-flight & practical readiness

Preferred mode: exa_or_http_fetch. No structured agent endpoint was found, and the page is not a readable document. Prefer a search index over raw HTML. shadeform.ai publishes no root agent discovery manifests, but docs.shadeform.ai serves /llms.txt (52 links). Probe docs.shadeform.ai or publish /.well-known/ard.json on shadeform.ai to link them.

Fetch: GET https://shadeform.ai/ No structured agent endpoint was found. Fetch the public page or use a search index.

Subdomain discovery hint (subdomain_stranded): shadeform.ai publishes no root agent discovery manifests, but docs.shadeform.ai serves /llms.txt (52 links). Probe docs.shadeform.ai or publish /.well-known/ard.json on shadeform.ai to link them. (check docs.shadeform.ai)

Practical readability: exa_parsable no, markdown negotiation no, render none, HTML quality none.

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

Readiness subscores: reach 20/20, readability 0/30, capabilities 0/35, conformance 10/15, total 30/100, grade C.

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