quicknode.com agentic web readiness

A+ Manifest validity: 78% (7/9 valid, 12 errors, 8 warnings) · Surface score 80 (coverage 60 + breadth 15 + conformance 5). 11 standards observed across 6 of 9 steps; 9 manifests present, 12 errors, 8 warnings. Checked 2026-10-23 14:56:46 UTC via www.quicknode.com. This grades the agent-facing files published at quicknode.com, not the organisation's products.

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

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 9727 02 IdentifyWebBotAuth 03 PermitContent Signals Policy, auth.md 04 Readllms.txt, AGENTS.md, 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	no entry has representativeQueries; ARD registries use 2-5 example queries to index entries
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 must be reverse-DNS with exactly one slash, e.g. com.example/weather 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 tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key)
Agent2Agent Protocol `/.well-known/agent-card.json`	errors	supportedInterfaces[0].protocolBinding missing supportedInterfaces[0].protocolVersion missing supportedInterfaces[1].protocolBinding missing supportedInterfaces[1].protocolVersion missing supportedInterfaces[2].protocolBinding missing supportedInterfaces[2].protocolVersion missing supportedInterfaces[3].protocolBinding missing supportedInterfaces[3].protocolVersion missing supportedInterfaces[4].protocolBinding missing supportedInterfaces[4].protocolVersion missing protocolVersion missing; clients cannot tell which A2A revision the card follows
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	valid
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`	absent HTTP 404
auth.md `/auth.md`	valid
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://mcp.quicknode.com/mcp (http), tools: list-endpoints, get-endpoint, create-endpoint, delete-endpoint, get-endpoint-metrics, list-endpoint-logs, get-endpoint-log-details, update-endpoint-rate-limits, list-endpoint-method-rate-limits, create-endpoint-method-rate-limit, update-endpoint-method-rate-limit, delete-endpoint-method-rate-limit, list-endpoint-security, update-endpoint-security-options, create-security-rule, delete-security-rule, get-rpc-usage, get-billing, list-chains — from /.well-known/mcp/server-card.json
A2A agent Quicknode Blockchain Agent at https://mcp.quicknode.com/mcp, skills: Autonomous Endpoint Provisioning, Blockchain RPC Call, Transaction Simulation, Token & Wallet Data, NFT Data & Metadata, Event & Log Decoding, Real-time Blockchain Streams, Blockchain SQL Explorer
API description https://www.quicknode.com/openapi.json (application/openapi+json)
API description https://www.quicknode.com/api-docs/v0/swagger.json (application/vnd.oai.openapi+json;version=3.0)
API description https://www.quicknode.com/docs (service-doc)
API description https://www.quicknode.com/openapi.json (application/openapi+json)
API description https://www.quicknode.com/agents.md (text/markdown)
API description https://www.quicknode.com/.well-known/x402.json (application/json)
API description https://x402.org (service-doc)
API description https://www.quicknode.com/openapi.json (application/openapi+json)
API description https://mpp.dev (service-doc)
llms.txt: Quicknode — Blockchain Data and Onchain Execution Platform, 136 links, llms-full.txt present
robots.txt AI policy: unlisted crawlers allowed

Standards observed

Agent2Agent Protocol https://quicknode.com/.well-known/agent-card.json
llms.txt https://quicknode.com/llms.txt
AGENTS.md https://quicknode.com/AGENTS.md
Content Signals Policy https://quicknode.com/robots.txt
Web Bot Auth HTTP Message Signatures https://quicknode.com/.well-known/http-message-signatures-directory
AI Catalog well-known file https://quicknode.com/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://quicknode.com/.well-known/api-catalog
auth.md https://quicknode.com/auth.md
Agent Skills https://quicknode.com/.well-known/agent-skills/index.json
Markdown for Agents https://quicknode.com/
AI Crawler User-Agent Tokens in robots.txt

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
security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

Agent pre-flight & practical readiness

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

Fetch: POST https://mcp.quicknode.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 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 5/15, total 90/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