#llmsmap.me

Independent technical audit

helius.dev

helius.dev

Overall AI readiness score

A combined result across all audit signals.

69of 100Average
AI readiness audit: 7/21/2026Public technical data

Overall AI readiness assessment

How ready helius.dev is for AI systems

69/100

Helius was independently audited by llmsmap. helius.dev currently scores 69/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 1,108 tokens. An expanded llms-full.txt is also available with 10,334 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 9 of 11 tracked AI bots are not blocked, while 2 receive a prohibition. Declared sitemaps: 2. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 44/100, Accessibility 93/100, Best Practices 77/100, SEO 85/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

  • Accessible llms.txt
  • Expanded llms-full.txt
  • 2 sitemap declarations
  • Strong Google agentic signals

Priority improvements

  1. 1Review the 2 explicit AI-bot blocks and keep only intentional restrictions.
  2. 2Add JSON-LD for the organisation, website, and core entities.
  3. 3Complete OpenGraph and canonical homepage metadata.
  4. 4Reduce mobile rendering delay and main-thread work.
llms.txt tokens1,108
llms-full.txt tokens10,334
ai.txt
sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse
44

Performance

93

Accessibility

77

Best Practices

85

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 44/100, with the largest visible content block appearing in 5.8 s and the browser main thread blocked for 1,270 ms. Layout shift was 0.007. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 93/100, Best Practices 77/100, and technical SEO 85/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

1

Improve interface contrast and readability

Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.

2

Clarify search and canonical signals

Verify unique titles and descriptions, crawlability, canonicals, descriptive link text, and language relationships. This reduces ambiguity for search engines and AI systems selecting a page.

3

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

FCP2.8 s

First content

LCP5.8 s

Main content

CLS0.007

Layout stability

TBT1,270 ms

Blocking time

SI6.5 s

Visual speed

Metric glossary
FCP · First content
When the first text or image appeared on screen.
LCP · Main content
When the largest visible element in the first viewport rendered.
CLS · Layout stability
How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time
How long the browser main thread could not respond quickly to input.
SI · Visual speed
How quickly the visible viewport filled with content.
7/21/2026Lighthouse 13.4.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://www.helius.dev/llms.txt
llms-full.txt

Full version is available

https://www.helius.dev/llms-full.txt
ai.txt

ai.txt file was not found

robots.txt

File found

https://helius.dev/robots.txt
Sitemap in robots.txt2

2 sitemaps found

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph

OpenGraph tags were not found on the homepage

AI bot access

Based on robots.txt analysis

GPTBotAllowed
OAI-SearchBotAllowed
ChatGPT-UserAllowed
Google-ExtendedAllowed
ClaudeBotAllowed
Claude-SearchBotAllowed
Claude-UserAllowed
BytespiderBlocked
CCBotBlocked
PerplexityBotAllowed
Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

# Helius

> Helius is Solana's leading infrastructure provider and developer platform. From high-performance RPC nodes and transaction sending (Sender) to gRPC streaming (LaserStream), webhooks, and digital asset APIs — Helius powers teams like Phantom, Jupiter, DFlow, Coinbase, and Bitwise.

This file is a directory. Each section below has its own llms.txt with detailed product info, examples, and use cases. Agents reading top-down can scope their consumption to the section they need.

## Section Indexes

- [Full agent context](https://www.helius.dev/llms-full.txt) — every product page, use case, signup flow, and the docs index inlined in one file for single-fetch ingestion
- [API catalog](https://www.helius.dev/api/llms.txt) — every Helius API surface with its OpenAPI spec and docs URL
- [Documentation](https://www.helius.dev/docs/llms.txt) — full developer docs and API reference
- [Use cases](https://www.helius.dev/use-case/llms.txt) — DeFi, exchanges, wallets, trading, fintech
- [Blog](https://www.helius.dev/blog/llms.txt) — research, tutorials, ecosystem updates
- [Staking](https://www.helius.dev/staking/llms.txt) — validator comparison and reward calculator

## Agent Surfaces

- [AGENTS.md](https://www.helius.dev/AGENTS.md) — agent onboarding doc
- [auth.md](https://www.helius.dev/auth.md) — authentication ceremony (API-key model, register/claim/revoke URIs)
- [CLI reference](https://www.helius.dev/cli.md) — full helius-cli command catalog and exit-code contract
- [Agent signup (Markdown)](https://www.helius.dev/api/agents.md) — programmatic API key acquisition
- [Agent signup (JSON)](https://www.helius.dev/api/agents.json) — machine-readable signup spec
- [Agent mode JSON](https://www.helius.dev/api/agent-mode) — structured product summary at one URL
- [MCP server card](https://www.helius.dev/.well-known/mcp/server-card.json) — MCP tool inventory and install metadata
- [A2A agent card](https://www.helius.dev/.well-known/agent-card.json) — A2A protocol manifest
- [OpenAPI catalog](https://www.helius.dev/openapi.json) — merged API spec across all surfaces
- [API catalog (RFC 9727)](https://www.helius.dev/.well-known/api-catalog) — discovery linkset

## Quick Install

- MCP server: `npx helius-mcp@latest`
- CLI: `npm install -g helius-cli` (also `npx helius-cli`)
- TypeScript SDK: `npm install helius-sdk`
- Rust SDK: `cargo add helius` ([crates.io](https://crates.io/crates/helius), [docs.rs](https://docs.rs/helius))
- API key (interactive): https://dashboard.helius.dev
- API key (programmatic): `helius signup --json` — 1 USDC on Solana mainnet
- Claude Code plugin: `/plugin marketplace add helius-labs/core-ai && /plugin install helius@helius-labs`

## Constraints

- **Authentication:** All Helius API endpoints require an API key passed as the `api-key` query parameter (e.g. `https://mainnet.helius-rpc.com/?api-key=YOUR_KEY`). Obtain one at https://dashboard.helius.dev or programmatically via `helius signup --json`.
- **Networks:** Solana mainnet (`mainnet.helius-rpc.com`) and devnet (`devnet.helius-rpc.com`) are supported across our RPC, API, and data streaming surfaces. Sender has 7 regional endpoints (`slc-`, `ewr-`, `lon-`, `fra-`, `ams-`, `sg-`, `tyo-` prefixes on `sender.helius-rpc.com`); LaserStream gRPC has its own 9-region footprint (Sender's 7 cities plus LAX and PITT — see https://www.helius.dev/laserstream for hostnames).
- **Agent signup is mainnet-only.** The autonomous `helius signup --json` flow requires a 1 USDC payment on Solana mainnet plus ~0.001 SOL for transaction fees. There is no devnet signup flow; once you have a key it works on both networks.
- **Rate limits vary by plan.** Free: 10 RPS, 1 sendTransaction/sec, 1M credits/month. Developer: 50 RPS, 5 sendTx/sec, 10M credits. Business: 200 RPS, 50 sendTx/sec, 5 sendBundle/sec, 100M credits. Professional: 500 RPS, 100 sendTx/sec, 5 sendBundle/sec, 200M credits. Full per-feature table: https://www.helius.dev/pricing.md.
- **MCP transport:** stdio only, distributed via npm (`npx helius-mcp@latest`). No hosted HTTP/SSE variant — see the [server card](https://www.helius.dev/.well-known/mcp/server-card.json) for the tool inventory and required `HELIUS_API_KEY` environment variable.
- **SLA:** 99.99% uptime. Live status at https://helius.statuspage.io/. Support response time scales with plan — Free: community, Developer: 24h, Business: 12h, Professional: 8h (+ Telegram + Slack).

Share or continue the analysis
Share this audit
Discuss with AI
Added 7/19/2026
helius.dev - AI readiness audit | llmsmap.me