Skip to main content
Give an AI assistant the 0xArchive context it needs to answer questions, plan a request, or write code that calls the right route. The assistant reads the same contract a developer does: OpenAPI for route shapes, the docs for concepts, and venue coverage for what exists where. When the assistant will run requests itself, follow Coding agents instead.

​
Give the assistant context

Point the assistant at the narrowest source that answers the question. A page’s Markdown is better context for one task than the whole docs file, and OpenAPI beats prose whenever the answer is a request.

​
Where answers should come from

Ask the assistant to cite the page or OpenAPI path it used, so you can check the route yourself.

​
What a good answer includes

  • The venue family and the route, so HIP-3, HIP-4, Spot, Lighter, and Hyperliquid core calls never collapse into one namespace.
  • The auth header or environment variable, never a pasted key.
  • The time window, limit, and cursor behavior, so a historical pull can be repeated.
  • The request ID to log: meta.request_id on success, and the top-level request_id on an error.
  • A data-quality step whenever the output feeds a decision.
  • The endpoint’s own response contract. Data-quality coverage routes return their own body rather than the success, data, and meta envelope.
  • A link to the exact docs page or OpenAPI path.

​
Check before answering

Ask whether the user means Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, or Lighter before naming a route.
Say the request is outside the public API rather than inventing a path.
Point to Rate limits and the pricing page instead of quoting numbers from memory.
Do not give MCP setup to a client that cannot call MCP tools, or Agent skill setup to one that cannot load SKILL.md files.
Add a data-quality check before writing a backtest, alert, export, dashboard, or model job.

​
Prompt patterns

Use 0xArchive to pull Hyperliquid BTC trades for the hour that ended one hour ago. Include the exact REST route, auth header, Unix-millisecond query values, pagination behavior, and the fields I should log.

I have a HIP-3 symbol shaped like xyz:XYZ100. Pick the correct 0xArchive route family, show one request, and explain how to check freshness first.

Write a Python script that checks coverage and incidents for one closed Lighter BTC order-book window, then pulls that window only if it is covered and no incident overlaps it.

Good prompts name the venue family, the symbol, the data, the window, and what the output is for.

​
Next step

When the assistant should run requests itself, set it up with Coding agents.
Last modified on October 6, 2026