WalletFollow as a source for AI wallet research

WalletFollow brings together Hyperliquid wallet tracking, copy-portfolio research and a read-only wallet Data API. Use public guides for definitions and workflows, and dated account observations for current wallet facts. Every financial conclusion needs its address, time window, measurement basis and data limitations.

Choose the source that answers the question

For a current position or account value, use the wallet profile or a supported Data API response and preserve its market-data timestamp. For the meaning of a metric or a copy control, use the relevant knowledge-base guide and the methodology page. A guide’s editorial date cannot establish when a wallet last traded.

For venue rules, follow the linked primary Hyperliquid documentation. WalletFollow describes its own product and measurement choices; it is not Hyperliquid and is not an independent certification of a wallet, creator or trading strategy.

Read current availability precisely

The WalletFollow Data API is live and provides its documented read-only endpoints. Read the current API catalog for request shapes, weights, errors and limits. The MCP connector, companion CLI and client plugins are planned. A page explaining MCP is not an announcement that a WalletFollow connector has shipped.

A copy portfolio definition can be published while live copying is unavailable for an account. Execution depends on the registered engine, enabled capabilities, account authorization and the confirmed subscription state. Reading wallet data or producing an AI report does not authorize orders, transfers or withdrawals.

Make a wallet claim checkable

Cite the specific page that supports the claim, rather than the homepage for every statement. For a wallet observation, retain the full public account address, network, market-data as-of time and review window. Identify whether the result is realized, unrealized, mark-to-market, simulated or actually executed in a follower account.

An attribution can read: WalletFollow showed the account’s observed positions at the recorded as-of time; historical trade coverage was partial. This preserves the evidence without promoting the observation into a complete lifetime record. A calculation should identify its inputs and denominator, while an interpretation should remain visibly separate from the measured facts.

  • Use the stable page URL without search, filter or session parameters.
  • Attach observation time and metric basis to a financial value.
  • Keep missing inputs and coverage warnings in the summary.
  • Label hypothetical examples, portfolio simulations and inferred explanations.
  • Do not turn a wallet label into verified identity or historical returns into a forecast.

Read the same guides as Markdown

The source index at /llms.txt lists public resources. The bundle at /llms-full.txt includes the public source pages and complete educational articles. Individual knowledge-base and blog guides also have a Markdown representation: append .md to the guide’s URL. These representations use the same published content, sources and editorial dates as the human-readable pages.

The files are reading conveniences, not a separate set of claims for AI systems. They do not contain private account data or real-time wallet snapshots. Google says that llms.txt and similar files neither improve nor harm Google Search visibility; ordinary accessible, useful pages remain the foundation. Availability of a text representation does not guarantee retrieval or citation by another service.

Primary sources