graphlit.com agentic web readiness

A Manifest validity: 100% (1/1 valid, 0 errors, 4 warnings) · Surface score 46 (coverage 30 + breadth 6 + conformance 10). 4 standards observed across 3 of 9 steps; 1 manifest present (+ robots.txt), 0 errors, 4 warnings. Checked 2026-10-25 19:16:59 UTC. This grades the agent-facing files published at graphlit.com, not the organisation's products.

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

Coverage by step

01 Discovernothing observed 02 Identifynothing observed 03 PermitOAuth Protected Resource and Authorization Server Metadata (as used for agent authorization), CIMD 04 Readllms.txt 05 Act 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
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) `/mcp/server-card`	absent	not fetched: disallowed_by_robots_txt
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid	no blockquote summary under the title
AGENTS.md `/AGENTS.md`	redirected → graphlit.dev	not fetched: redirect off-host to graphlit.dev
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`	absent HTTP 404
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`	absent HTTP 404
auth.md `/auth.md`	redirected → graphlit.dev	not fetched: redirect off-host to graphlit.dev
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://graphlit.com/mcp (streamable-http) — from /.well-known/oauth-protected-resource
llms.txt: Graphlit, 34 links
robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)
OAuth protected resource https://graphlit.com/mcp, authorization servers: https://graphlit.com

Standards observed

llms.txt https://graphlit.com/llms.txt
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://graphlit.com/.well-known/oauth-protected-resource
OAuth Client ID Metadata Document https://graphlit.com/.well-known/oauth-authorization-server
Model Context Protocol

Cheapest next steps

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": "graphlit.com"}))

AGENTS.md: instructions for coding agents working on or with the site

Generate starter /AGENTS.md for graphlit.com

# Graphlit for agents

Graphlit and what it offers to agents

## Read the data, not the HTML
- Index: https://graphlit.com/llms.txt
- API description: https://graphlit.com/openapi.json
- Discovery catalog: https://graphlit.com/.well-known/ard.json

## Calling
- MCP server (Streamable HTTP): https://graphlit.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@graphlit.com

api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "graphlit.com"}))

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback llms_txt). Call the MCP endpoint at https://graphlit.com/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://graphlit.com/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

Practical readability: exa_parsable yes, markdown negotiation no, render csr_hydration_trapped, HTML quality js_shell, HTML-to-llms.txt token ratio 4.275×.

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

Readiness subscores: reach 20/20, readability 10/30, capabilities 18/35, conformance 10/15, total 58/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