# Status State API – Hyperliquid Monitor

> Status State API – Hyperliquid Monitor is a paid API for AI agents from status-state-api.replit.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Returns the current normalized operational status of Hyperliquid, including component health, active incidents, and poll metadata, paid per-call via USDC microtransaction.

## Facts

- Endpoint: GET https://status-state-api.replit.app/api/monitors/hyperliquid?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/status-state-api-hyperliquid-monitor-1ca99be4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iaCf7y56W7VlZXpUjsiec

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 status-state-api-hyperliquid-monitor-1ca99be4
```

Example prompt: Is Hyperliquid up right now? Check its current status and let me know if there are any active incidents or degraded components.

## When to prefer this

Choose this endpoint when you specifically need Hyperliquid's operational status with fault-first component breakdown and incident detail, in a no-signup, pay-per-call context via USDC on Base or Solana. Prefer it over scraping Hyperliquid's own status page when you need a normalized, structured JSON response ready for agent consumption. Use it when you need the hasActiveIncident flag available before committing to the full paid response.

## Known failure modes

- Payment not received or invalid USDC transaction — request rejected with 402
- Invalid or unknown slug returns 404 or error body
- Upstream status page is stale — staleness object indicates lag
- Network timeout from upstream status page results in null lastCheckedAt
- Replit hosting cold-start may cause occasional latency spikes

## How this service works

Current normalized overall status, fault-first components, active incident (or closedIncidentSummary if stale), and poll clocks. overallStatus and hasActiveIncident are in the 402 JSON body so you can decide whether to pay. $0.01 per call in USDC on Base or Solana, verified and settled by the PayAI facilitator - no API key, no signup.

## Output

A JSON object containing: normalized overallStatus string (e.g. 'operational', 'degraded', 'outage'), an array of components sorted fault-first with their individual statuses, an activeIncident object (or null if none), a closedIncidentSummary if the last incident recently closed, lastCheckedAt and sourceUpdatedAt timestamps, staleness metadata, and checkIntervalMinutes. overallStatus and hasActiveIncident are also exposed in the 402 response body before payment is committed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "slug"
     ],
     "properties": {
      "slug": {
       "type": "string",
       "pattern": "^[a-z0-9-]{1,64}$",
       "examples": [
        "openai"
       ],
       "description": "Vendor slug from the free GET /api/monitors catalog"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "slug",
      "name",
      "overallStatus",
      "components",
      "activeIncident",
      "lastCheckedAt",
      "sourceUpdatedAt",
      "staleness"
     ],
     "properties": {
      "name": {
       "type": "string"
      },
      "slug": {
       "type": "string"
      },
      "staleness": {
       "type": "object"
      },
      "components": {
       "type": "array"
      },
      "homepageUrl": {
       "type": "string"
      },
      "lastCheckedAt": {
       "type": [
        "string",
        "null"
       ]
      },
      "overallStatus": {
       "type": "string"
      },
      "activeIncident": {
       "type": [
        "object",
        "null"
       ]
      },
      "sourceUpdatedAt": {
       "type": [
        "string",
        "null"
       ]
      },
      "componentsOmitted": {
       "type": [
        "object",
        "null"
       ]
      },
      "checkIntervalMinutes": {
       "type": "number"
      },
      "closedIncidentSummary": {
       "type": [
        "object",
        "null"
       ]
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/status-state-api-hyperliquid-monitor-1ca99be4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from status-state-api.replit.app](https://www.zero.xyz/host/status-state-api.replit.app/llms.txt)