Hyperliquid

Last scanned hyperliquid.gitbook.io/hyperliquid-docsGitBook15 pages tested

AI agents can find, read and use these docs well. Hyperliquid scores 95 out of 100 (grade A), passing 20 of 26 checks. 6 still need work.

Fix it with Documentation.AI

Get this report by email

We send the full report to your inbox. Nothing on this page needs an email.

Use your work email. We only send what you asked for, and every email has an unsubscribe link.

Developer docs

Kind of site

20/26

Checks passed

4

Partly passed

2

Failed

Access

Content discoverability5 passed2 partly
  • llms.txt follows the standard structure

    llms.txt contains parseable links but doesn't fully follow the proposed structure: https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt: No blockquote summary found

    Your llms.txt contains parseable links but doesn't follow the standard structure. Add an H1 title as the first line and a blockquote summary (lines starting with >) to improve agent parsing.

    Check your fix: llms.txt starts with a # Title, then a > summary line, then ## sections of links.

  • Pages point agents to llms.txt

    llms.txt directive found in HTML of 15 of 15 sampled pages, but buried deep in the page (past 50%)

    An llms.txt directive was found in the HTML of some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every documentation page.

    Check your fix: curl -s https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid | grep -n llms.txt finds the link near the top of the HTML.

  • llms.txt exists

    llms.txt found at 2 locations; using https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt as canonical

  • llms.txt fits in an agent's context

    llms.txt is 21,199 characters (under 50,000 threshold)

  • llms.txt links work

    All 15 same-origin sampled links resolve (149 total links)

  • llms.txt links point to Markdown

    15/15 same-origin sampled links point to markdown content (100%)

  • Markdown pages point agents to llms.txt

    llms.txt directive found in markdown of all 15 sampled pages, near the top of content

Markdown availability2 passed
  • Pages are available as Markdown

    15/15 sampled pages support .md URLs (100%)

  • Server returns Markdown when asked

    15/15 sampled pages support content negotiation (100%)

Page size and truncation3 passed1 failed
  • Content starts near the top

    14 of 15 sampled pages have content starting past 50% (worst 86%)

    14 of 15 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.

  • Content is in the HTML without JavaScript

    All 15 sampled pages contain server-rendered content

  • Markdown pages fit in context

    All 15 pages under 50K chars (median 2K, max 32K)

  • HTML pages fit in context

    All 15 sampled pages under 50K chars (median 395K HTML → 6K markdown (98% boilerplate))

Content structure2 passed
  • Headings inside tabs name their variant

    1 page(s) with tabs found, but no section headers inside tab panels to evaluate

  • Tabs don't bloat the page

    16 tab group(s) across 1 of 15 sampled pages; all serialize under 50K chars

  • Code blocks are well-formed

    All 20 code fences properly closed across 17 pages

URL stability2 passed
  • Missing pages return a real 404

    All 15 sampled pages return proper error codes for bad URLs

  • Redirects stay on the same host

    All 2 redirect(s) across 15 sampled pages are same-host HTTP redirects

Content health1 passed1 failed1 partly
  • Markdown matches the HTML page

    1 of 15 pages have substantive content differences between markdown and HTML (avg 6% missing)

    1 pages have substantive content differences between markdown and HTML (avg 6% missing). If unintentional, agents are getting outdated content; regenerate markdown from source or fix the build pipeline.

  • Cache headers allow timely updates

    17 of 17 endpoints have moderate cache lifetimes (1–24 hours)

    17 endpoints have moderate cache lifetimes (1-24 hours). Updates to llms.txt or markdown content may take hours to propagate. Consider reducing cache lifetimes for these resources.

  • llms.txt covers the whole site

    llms.txt covers 98% of 149 sitemap doc pages; 3 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)

Authentication and access1 passed
  • Gated docs offer another way in

    All docs pages are publicly accessible; no alternative access paths needed

  • Docs are readable without logging in

    All 15 sampled pages are publicly accessible

Crawler access2 passed
  • Crawlers and AI assistants may read the docs

    robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.

  • Sitemap lists the docs pages

    The sitemap at https://hyperliquid.gitbook.io/hyperliquid-docs/sitemap.xml lists 148 of the 151 docs pages found through llms.txt and page links.

Freshness

Maintenance2 passed1 partly
  • Links and section anchors work

    1 of 54 references checked on the sampled pages are broken: 1 link. 1 more could not be verified (timeouts or blocked requests) and is not counted.

    Fix or remove the broken links, redirect moved pages to their new address, and restore or retarget section anchors. Agents follow links to gather context, and a dead link ends that path.

    Check your fix: Every link on https://purrsec.com/address/0x9b498c3c8a0b8cd8ba1d9851d40d186f1872b44e (404) linked from https://hyperliquid.gitbook.io/hyperliquid-docs/support/faq/hyperevm-issues/cant-see-my-hyperevm-assets-in-wallet-extension returns 200, and every #section link points at an element with that id.

  • Pages say when they were last changed

    15 of 15 sampled pages state when they were last changed.

  • Sitemap entries still exist

    All 10 sitemap entries sampled still exist.

Consistency with the API specNot applicable
  • Endpoints in the docs exist in the API spec

    No OpenAPI description was found, so the docs could not be compared with a spec.

CurrencyNot applicable
  • Deprecated operations are marked as such

    No OpenAPI description was found, so deprecation notices could not be compared with a spec.

Additional checks

Not part of the score: optional extras that help agents use your docs.

  • MCP server is discoverable

    An MCP server is described at https://hyperliquid.gitbook.io/hyperliquid-docs/.well-known/mcp/server-card.json.

  • llms-full.txt is available

    llms-full.txt found at https://hyperliquid.gitbook.io/hyperliquid-docs/llms-full.txt (532,300 characters).

  • Agent skills are published

    No agent skills index was found at /.well-known/agent-skills/index.json.

    Publish an Agent Skills index at /.well-known/agent-skills/index.json with a SKILL.md for your main tasks, so agents can load task instructions without reading every page.

About this scan

Scanned
Oct 21, 2026
Pages tested
15 of 149 found
Platform
GitBook
Kind of site
Developer docs
AFDocs score, on its own
95 (A), 16 of 23 checks pass
  • Based on 15 sampled pages, chosen deterministically from the sitemap and llms.txt. Pages outside the sample were not read.
  • Pages were fetched without running JavaScript, the way most AI agents read the web.
  • Answerability, where an AI agent answers real questions written from these pages, runs in the open-source scanner with your own API key. This web score is made of Access and Freshness.

Methodology 2026-09.6 · AFDocs 0.20.0

Pages we sampled (15)
  • https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid
  • https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api
  • https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint/perpetuals
  • https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/websocket
  • https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/raw-hyperevm-block-data
  • https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/clearinghouse
  • https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/vaults/for-vault-leaders-legacy
  • https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-4-outcome-markets
  • https://hyperliquid.gitbook.io/hyperliquid-docs/referrals/proposal-staking-referral-program
  • https://hyperliquid.gitbook.io/hyperliquid-docs/support/faq/deposit-or-transfer-issues-missing-lost/deposited-via-avalanche-network
  • https://hyperliquid.gitbook.io/hyperliquid-docs/support/faq/hyperevm-issues/cant-see-my-hyperevm-assets-in-wallet-extension
  • https://hyperliquid.gitbook.io/hyperliquid-docs/support/faq/trade-outcome-looks-incorrect/why-was-i-liquidated
  • https://hyperliquid.gitbook.io/hyperliquid-docs/support/read-me-support-guide
  • https://hyperliquid.gitbook.io/hyperliquid-docs/trading/hyperps
  • https://hyperliquid.gitbook.io/hyperliquid-docs/trading/portfolio-graphs

Show your score

Add the badge to your docs or README. It updates each time the site is scanned.

Agent Readiness Score badge

Markdown

[![Agent Readiness Score: 95 (A)](https://documentation.ai/agent-score/badge/hyperliquid.svg)](https://documentation.ai/agent-score/hyperliquid)

HTML

<a href="https://documentation.ai/agent-score/hyperliquid"><img src="https://documentation.ai/agent-score/badge/hyperliquid.svg" alt="Agent Readiness Score: 95 (A)" height="20"></a>

Agent-ready docs by default

Documentation.AI sites ship with llms.txt, Markdown pages, a sitemap and an MCP server, and our agent keeps the content current.

Live in under 5 min · No credit card required