kysely.dev agentic web readiness

A Manifest validity: 75% (3/4 valid, 1 error, 8 warnings) · Surface score 59 (coverage 40 + breadth 9 + conformance 10). 5 standards observed across 4 of 9 steps; 4 manifests present (+ robots.txt), 1 error, 8 warnings. Checked 2026-10-25 22:03:31 UTC. This grades the agent-facing files published at kysely.dev, not the organisation's products.

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

Coverage by step

01 DiscoverARD, AI Catalog well-known file 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt 05 ActAgent Skills 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	valid	entries is empty: the catalog advertises nothing no entry has representativeQueries; ARD registries use 2-5 example queries to index entries host block missing (displayName, identifier, documentationUrl help clients name the publisher)
AI Catalog well-known file `/.well-known/ai-catalog.json`	valid	entries is empty: the catalog advertises nothing no entry has representativeQueries; ARD registries use 2-5 example queries to index entries host block missing (displayName, identifier, documentationUrl help clients name the publisher)
MCP Server Cards (SEP-2127) `/mcp/server-card`	absent HTTP 404
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	errors	skills is empty View valid `/.well-known/agent-skills/index.json` template for kysely.dev { "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json", "skills": [ { "name": "kysely", "type": "skill-md", "description": "Kysely and what it offers to agents", "url": "https://kysely.dev/.well-known/agent-skills/kysely/SKILL.md", "digest": "sha256:0000000000000000000000000000000000000000000000000000000000000000" } ] }
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 (allowed) no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

llms.txt: Kysely, 79 links, llms-full.txt present
robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed
ARD bridge (/.well-known/ard.json): 0/0 valid, 0 legacy, 0 dead/broken

Standards observed

llms.txt https://kysely.dev/llms.txt
Content Signals Policy https://kysely.dev/robots.txt
Agentic Resource Discovery https://kysely.dev/.well-known/ard.json
AI Catalog well-known file https://kysely.dev/.well-known/ai-catalog.json
Agent Skills https://kysely.dev/.well-known/agent-skills/index.json

Cheapest next steps

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

Generate starter /AGENTS.md for kysely.dev

# Kysely for agents

Kysely and what it offers to agents

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

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

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": "kysely.dev"}))

security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

Generate starter /.well-known/security.txt for kysely.dev

Contact: mailto:security@kysely.dev
Expires: 2027-09-20T22:03:31Z
Canonical: https://kysely.dev/.well-known/security.txt
Preferred-Languages: en
Policy: https://kysely.dev/security-policy

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://kysely.dev/llms.txt GET /llms.txt and follow its links.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 15163, HTML-to-llms.txt token ratio 6.155×, JSON-LD SoftwareApplication, Organization, PostalAddress, ContactPoint.

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

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