dragonflydb.io agentic web readiness

C Manifest validity: 50% (1/2 valid, 1 error, 5 warnings) · Surface score 20 (coverage 10 + breadth 0 + conformance 10). 1 standard observed across 1 of 9 steps; 2 manifests present (+ robots.txt), 1 error, 5 warnings. Checked 2026-10-25 23:45:50 UTC via www.dragonflydb.io. This grades the agent-facing files published at dragonflydb.io, not the organisation's products.

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

Coverage by step

Manifests

# Dragonflydb

> Dragonflydb 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://dragonflydb.io/docs/getting-started): the first page to read
- [API reference](https://dragonflydb.io/openapi.json): OpenAPI description

## Optional
- [Changelog](https://dragonflydb.io/changelog): what changed, newest first

What an agent can call

• llms.txt: untitled, 208 links
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)

Standards observed

• AGENTS.md https://dragonflydb.io/AGENTS.md

Cheapest next steps

1. 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": "dragonflydb.io"}))
2. 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": "dragonflydb.io"}))
3. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
   Generate starter /.well-known/security.txt for dragonflydb.io

   Contact: mailto:security@dragonflydb.io
   Expires: 2027-09-20T23:45:50Z
   Canonical: https://dragonflydb.io/.well-known/security.txt
   Preferred-Languages: en
   Policy: https://dragonflydb.io/security-policy
   

Agent pre-flight & practical readiness

Preferred mode: exa_or_http_fetch. No structured agent endpoint was found. The page has readable text, so fetch it directly or through a search index.

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

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 59597, HTML-to-llms.txt token ratio 4.15×, JSON-LD Organization, WebPage, BreadcrumbList, ListItem.

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

Readiness subscores: reach 20/20, readability 22/30, capabilities 0/35, conformance 10/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