Hl Portfolio X402

What is Hl Portfolio X402?

Hl Portfolio X402 is an MCP server that analyzes Hyperliquid perpetuals accounts, providing positions, PnL, fills, open orders, and funding. It uses x402 pay-per-call micropayments (USDC on Base L2) with no API key, signup, or rate-limit wall, part of the klymax402 marketplace.

How to use Hl Portfolio X402?

Add the server to your MCP client config (e.g., Claude Desktop, Cursor, ElizaOS) with the URL https://hl-portfolio.api.klymax402.com/mcp. Use the x402 protocol for HTTP calls; any x402-aware client handles the payment challenge automatically.

Key features of Hl Portfolio X402

• Pay-per-call via x402 (USDC on Base L2) – no signup.
• Four tools: account state, trade fills, open orders, funding.
• Returns full clearinghouse state for any Hyperliquid wallet.
• Each tool costs $0.002–$0.003 per call.
• Part of the klymax402 marketplace of 100 x402 APIs.

Use cases of Hl Portfolio X402

• Analyzing a trader's risk exposure and margin health.
• Evaluating portfolio allocation on Hyperliquid for copy trading.
• Retrieving recent trade executions with realized PnL.
• Monitoring open orders and pending limit orders.
• Calculating funding income/expense and carry trade profitability.

FAQ from Hl Portfolio X402

What is the x402 protocol and how does payment work?

x402 is an HTTP-native pay-per-call protocol. The server responds with a 402 Payment Required challenge, and an x402-aware client automatically signs, pays (USDC on Base L2), and retries the request.

What are the tools and their costs?

hyperliquid_get_account_state ($0.003), hyperliquid_get_trade_fills ($0.003), hyperliquid_get_open_orders ($0.002), hyperliquid_get_user_funding ($0.002). Each requires a wallet address parameter.

Is there any API key or signup required?

No. The x402 protocol handles authentication and payment directly, with no API key, signup, or rate limits.

Where does the data come from and are there any limits?

Data is fetched from Hyperliquid on-chain state. The limit parameter for trade fills defaults to 20 and maxes at 100; funding startTime defaults to last 7 days.

What transports and authentication are supported?

The server uses MCP (Model Context Protocol) and REST via x402. Authentication is handled by the x402 payment challenge; it is also reachable via ATXP (OAuth-wrapped x402).