AI & MCP
Connect an AI assistant to Hyperliquid wallet data
A supported coding assistant can research wallets through WalletFollow’s read-only Data API when you give its secure runtime access to a Data API key. Read the API catalog first, request the named wallet, preserve timestamps and coverage, then ask for an evidence-based summary. The MCP connector is planned.
Establish the data contract first
Open the current API page and create a Data API key in the account console. Configure that key through the assistant’s supported secret or environment mechanism. Do not paste its value into a public prompt, repository or report. A data key is a service credential, not a wallet private key.
Ask the assistant to retrieve GET /v1/catalog before building requests. The catalog describes the supported endpoints, weights, plans, errors and headers. Reading it avoids inventing capabilities from old examples or a proposed MCP tool list.
Retrieve one wallet before scaling up
The wallet endpoint is GET /v1/wallets/{address}. The address must be a complete 0x-prefixed account address. Adding include=trades requests the supported trade-analysis variant and has a higher request weight than the summary. Use the response’s stated schema rather than assuming every metric is available for every wallet.
Ask for the account summary and positions first. Request trade analysis when the question needs historical activity. This keeps the workflow focused and reduces unnecessary use of the account budget.
Control usage and failure behaviour
Use GET /v1/usage and the response headers to inspect the account’s remaining budget. Respect Retry-After on rate-limit responses. A 401 means authentication needs attention; repeatedly retrying it does not fix the credential. A coverage gap or upstream error should be reported as unavailable evidence, not silently replaced by a plausible value.
Start with a small, explicit address list. Deduplicate requests and cache observations only for a period suitable for the task. A long-lived cache may work for a historical note but be unsuitable for a current exposure question.
Ask for an auditable answer
A good final report names the address, observation time, review window and metric basis. It separates observed positions from interpretations and explains missing inputs. The supported data workflow does not authorize trading, transfers or withdrawals. If an assistant proposes an action, review it as a separate decision rather than treating the data connection as account permission.
- Read the catalog and current API instructions.
- Configure credentials outside the conversation text.
- Retrieve only the evidence needed.
- Require timestamps, coverage and source values in the report.