# ScriptMasterLabs Hyperliquid Meta API

> ScriptMasterLabs Hyperliquid Meta API is a paid API for AI agents from acp-x402-discovery.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Retrieves Hyperliquid exchange metadata including market configurations, asset listings, and trading parameters via pay-per-call x402 micropayment.

## Facts

- Endpoint: GET https://acp-x402-discovery.onrender.com/x402/hyperliquid-meta
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scriptmasterlabs-hyperliquid-meta-api-9ef956b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IOELYUiVtEwHDJHxe6o5_

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability scriptmasterlabs-hyperliquid-meta-api-9ef956b4
```

Example prompt: Can you pull the current Hyperliquid exchange metadata — I want to see what assets and trading pairs are listed on the platform right now?

## When to prefer this

Use this endpoint when you need programmatic access to Hyperliquid exchange metadata (asset universe, market configs, perpetual specs) and are operating in a crypto-native agent stack that supports x402 micropayments settled in USDC on Base. Prefer this over scraping Hyperliquid directly when you need a pay-per-call API abstraction. Not suitable if you need real-time order book data, trade history, or position management.

## Known failure modes

- Payment not settled in USDC on Base — 402 response returned requiring payment
- Invalid or malformed properties filter parameter — may return empty or unexpected results
- Hyperliquid upstream API unavailable — server error or timeout
- No schema validation enforced — malformed input may be silently ignored
- Render.com cold start latency — first request may timeout if service is idle

## How this service works

Pay-per-call crypto, RWA, federal, SEC, and compliance APIs. Settled in USDC on Base via x402. Hyphen routes only (e.g. /x402/rwa-aggregates, /x402/gas-tracker).

## Output

Returns Hyperliquid exchange metadata including the universe of supported assets, perpetual contract specs, trading parameters, and market configurations as a JSON object.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scriptmasterlabs-hyperliquid-meta-api-9ef956b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from acp-x402-discovery.onrender.com](https://www.zero.xyz/host/acp-x402-discovery.onrender.com/llms.txt)
