What is helius.dev's AI agent readiness grade?

helius.dev publishes 12 agent-facing standards across 5 of 9 lifecycle steps (grade A+, checked 2026-10-25).

Which AI agent discovery manifests and crawler policies does helius.dev publish?

helius.dev publishes 12 observed agentic-web standards (Agent2Agent Protocol, llms.txt, AGENTS.md, Content Signals Policy, Agentic Resource Discovery, AI Catalog well-known file, api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs, auth.md, AI Crawler User-Agent Tokens in robots.txt, Markdown for Agents, MCP Server Cards (SEP-2127), Model Context Protocol). Preferred agent routing mode: mcp.

helius.dev agentic web readiness

A+ Manifest validity: 100% (9/9 valid, 0 errors, 11 warnings) · Surface score 80 (coverage 50 + breadth 15 + conformance 15). 12 standards observed across 5 of 9 steps; 9 manifests present (+ security.txt), 0 errors, 11 warnings. Checked 2026-10-25 13:55:49 UTC via www.helius.dev. This grades the agent-facing files published at helius.dev, not the organisation's products.

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

Coverage by step

01 DiscoverARD, AI Catalog well-known file, RFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy, auth.md, AI Crawler User-Agent Tokens in robots.txt 04 Readllms.txt, AGENTS.md, Markdown for Agents 05 Act 06 CoordinateA2A 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	valid
AI Catalog well-known file `/.well-known/ai-catalog.json`	valid
MCP Server Cards (SEP-2127) `/.well-known/mcp/server-card.json`	valid	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[] $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json 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`	valid	supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape protocolVersion is "0.3.0" (pre-1.0 legacy shape; A2A 1.0 uses protocolVersion "1.0" and supportedInterfaces[]) declared A2A endpoint https://www.helius.dev is not a callable agent endpoint (agent card url points to the HTML homepage rather than a callable A2A endpoint)
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	valid
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`	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://www.npmjs.com/package/helius-mcp, tools: heliusAccount, heliusWallet, heliusAsset, heliusTransaction, heliusChain, heliusStreaming, heliusKnowledge, heliusWrite, heliusCompression, expandResult — from /.well-known/mcp/server-card.json
A2A agent Helius for Agents at https://www.helius.dev, skills: Solana RPC, Digital Asset Standard (DAS) API, Helius Sender & Priority Fees, Enhanced Transactions, LaserStream gRPC & WebSockets, Webhooks, Wallet Intelligence, Agentic API Key Signup
API description https://www.helius.dev/openapi.json (application/openapi+json)
API description https://www.helius.dev/openapi.json (application/openapi+json)
API description https://www.helius.dev/openapi/enhanced-api.json (application/json)
API description https://www.helius.dev/docs/enhanced-transactions/overview (text/html)
API description https://www.helius.dev/openapi/index.json (application/json)
API description https://www.helius.dev/openapi/rpc-http.json (application/json)
API description https://www.helius.dev/docs/rpc/guides/overview (text/html)
API description https://www.helius.dev/openapi/das-api.json (application/json)
API description https://www.helius.dev/docs/das-api (text/html)
API description https://www.helius.dev/openapi/sender-api.json (application/json)
API description https://www.helius.dev/docs/sending-transactions/sender (text/html)
API description https://www.helius.dev/openapi/wallet-api.json (application/json)
API description https://www.helius.dev/docs/wallet-api/overview (text/html)
API description https://www.helius.dev/openapi/priority-fee-api.json (application/json)
API description https://www.helius.dev/docs/priority-fee-api (text/html)
API description https://www.helius.dev/openapi/zk-compression.json (application/json)
API description https://www.helius.dev/docs/zk-compression/introduction (text/html)
API description https://www.helius.dev/openapi/admin-api.json (application/json)
API description https://www.helius.dev/docs/api-reference/admin (text/html)
API description https://www.helius.dev/openapi/webhooks.json (application/json)
llms.txt: Helius, 53 links, llms-full.txt present
robots.txt AI policy: blocks Bytespider; unlisted crawlers partial
Endpoint check (a2a https://www.helius.dev): pseudo_endpoint_html (agent card url points to the HTML homepage rather than a callable A2A endpoint)
ARD bridge (/.well-known/ard.json): 1/3 valid, 1 legacy, 0 dead/broken

Standards observed

Agent2Agent Protocol https://helius.dev/.well-known/agent-card.json
llms.txt https://helius.dev/llms.txt
AGENTS.md https://helius.dev/AGENTS.md
Content Signals Policy https://helius.dev/robots.txt
Agentic Resource Discovery https://helius.dev/.well-known/ard.json
AI Catalog well-known file https://helius.dev/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://helius.dev/.well-known/api-catalog
auth.md https://helius.dev/auth.md
AI Crawler User-Agent Tokens in robots.txt https://helius.dev/robots.txt
Markdown for Agents https://helius.dev/
MCP Server Cards (SEP-2127)
Model Context Protocol

Cheapest next steps

No cheap file is missing, or the origin never answered.

Agent pre-flight & practical readiness

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

Fetch: POST https://www.npmjs.com/package/helius-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 partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.

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