surrealdb.com agentic web readiness

A+ Manifest validity: 89% (8/9 valid, 4 errors, 5 warnings) · Surface score 75 (coverage 50 + breadth 15 + conformance 10). 10 standards observed across 5 of 9 steps; 9 manifests present, 4 errors, 5 warnings. Checked 2026-10-23 16:02:30 UTC. This grades the agent-facing files published at surrealdb.com, not the organisation's products.

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

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy, auth.md, AI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, Markdown for Agents 05 ActAgent Skills 06 CoordinateA2A 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`	valid
MCP Server Cards (SEP-2127) `/.well-known/mcp/server-card.json`	errors	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) name missing version missing description missing Content-Type is application/json; charset=utf-8; SEP-2127 says serve application/mcp-server-card+json pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[] remotes missing: a card with no remotes gives clients nothing to connect to
Agent2Agent Protocol `/.well-known/agent-card.json`	valid	protocolVersion missing; clients cannot tell which A2A revision the card follows
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	valid
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	valid
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	valid
auth.md `/auth.md`	valid
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://mcp.surrealdb.com (streamable-http) — from /.well-known/mcp/server-card.json
A2A agent SurrealDB MCP Server at https://mcp.surrealdb.com, skills: Cloud instance management, SurrealQL query execution, Schema and catalogue inspection, Instance monitoring and diagnostics, Organisation and access management, Billing, usage and cost estimation, Agent memory with Spectron
API description https://api.surrealdb.com/openapi/public.yaml (application/openapi+yaml)
API description https://surrealdb.com/.well-known/api-catalog (application/linkset+json)
API description https://surrealdb.com/openapi.json (application/json)
API description https://surrealdb.com/docs (text/html)
API description https://api.surrealdb.com/openapi/public.yaml (text/yaml)
API description https://api.surrealdb.com/docs (text/html)
API description https://api.surrealdb.com/.well-known/oauth-protected-resource (application/json)
API description https://api.surrealdb.com/.well-known/oauth-authorization-server (application/json)
API description https://surrealdb.com/.well-known/mcp/server-card.json (application/json)
API description https://surrealdb.com/.well-known/agent-card.json (application/json)
API description https://surrealdb.com/docs/build/ai-agents/mcp (text/html)
API description https://mcp.surrealdb.com/.well-known/oauth-protected-resource (application/json)
API description https://mcp.surrealdb.com/.well-known/oauth-authorization-server (application/json)
API description https://surrealdb.sh (text/html)
llms.txt: SurrealDB, 171 links, llms-full.txt present
robots.txt AI policy: allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Google-Extended, PerplexityBot, Applebot-Extended, Amazonbot; unlisted crawlers allowed
OAuth protected resource https://surrealdb.com, authorization servers: https://surrealdb.com

Standards observed

Agent2Agent Protocol https://surrealdb.com/.well-known/agent-card.json
llms.txt https://surrealdb.com/llms.txt
Content Signals Policy https://surrealdb.com/robots.txt
AI Catalog well-known file https://surrealdb.com/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://surrealdb.com/.well-known/api-catalog
auth.md https://surrealdb.com/auth.md
AI Crawler User-Agent Tokens in robots.txt https://surrealdb.com/robots.txt
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://surrealdb.com/.well-known/oauth-protected-resource
Agent Skills https://surrealdb.com/.well-known/agent-skills/index.json
Markdown for Agents https://surrealdb.com/

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
AGENTS.md: instructions for coding agents working on or with the site

Agent pre-flight & practical readiness

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

Fetch: POST https://mcp.surrealdb.com 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 yes, render markdown_native, HTML quality high, first content at byte 0.

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

Readiness subscores: reach 20/20, readability 30/30, capabilities 35/35, conformance 10/15, total 95/100, grade A+.

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