turnkey.com agentic web readiness

D Manifest validity: 0% (0/1 valid, 2 errors, 5 warnings) · Surface score 10 (coverage 10 + breadth 0 + conformance 0). 1 standard observed across 1 of 9 steps; 1 manifest present (+ security.txt), 2 errors, 5 warnings. Checked 2026-10-25 23:41:33 UTC via www.turnkey.com. This grades the agent-facing files published at turnkey.com, not the organisation's products.

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

Coverage by step

Manifests

# 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://turnkey.com/sitemap.xml
Agentmap: https://turnkey.com/.well-known/ard.json

Contact: mailto:security@turnkey.com
Expires: 2027-09-20T23:41:33Z
Canonical: https://turnkey.com/.well-known/security.txt
Preferred-Languages: en
Policy: https://turnkey.com/security-policy

What an agent can call

• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers unspecified

Standards observed

• Markdown for Agents https://turnkey.com/

Cheapest next steps

1. llms.txt: one Markdown index file; the most widely read agent-facing file
   Generate starter /llms.txt for turnkey.com

   # Turnkey
   
   > Turnkey 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://turnkey.com/docs/getting-started): the first page to read
   - [API reference](https://turnkey.com/openapi.json): OpenAPI description
   
   ## Optional
   - [Changelog](https://turnkey.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": "turnkey.com"}))
3. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for turnkey.com

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

Agent pre-flight & practical readiness

Preferred mode: markdown_negotiation. GET / with Accept: text/markdown. The origin already serves a Markdown body for agents. turnkey.com publishes no root agent discovery manifests, but docs.turnkey.com serves /llms.txt (26 links). Probe docs.turnkey.com or publish /.well-known/ard.json on turnkey.com to link them.

Fetch: GET https://turnkey.com/ GET / with Accept: text/markdown. The origin negotiates a Markdown body.

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

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 unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.

Readiness subscores: reach 20/20, readability 30/30, capabilities 2/35, conformance 0/15, total 52/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