# Laevitas WebSocket Hourly Pass

> Laevitas WebSocket Hourly Pass is a paid API for AI agents from apiv2.laevitas.ch, paid per call via x402, $0.5/call, status unknown (last checked 2026-09-14).

Issues a one-hour WebSocket access pass token for authenticated streaming of Laevitas crypto derivatives market data.

## Facts

- Endpoint: POST https://apiv2.laevitas.ch/api/v1/x402/ws-pass/hour
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/laevitas-websocket-pass-hourly-token-5e539875
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-UMEEglhXxiWVibjzkxZ4

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 laevitas-websocket-pass-hourly-token-5e539875 -d '<json body>'
```

Example prompt: I need to stream live crypto options and derivatives data from Laevitas for the next hour — can you buy me an hourly WebSocket pass so I can connect to their real-time feed?

## When to prefer this

Use this endpoint when you need real-time streaming access to Laevitas crypto derivatives data via WebSocket and want to pay per-hour rather than maintaining a long-term API subscription. Ideal for short-duration data collection sessions, one-off analysis tasks, or when testing Laevitas streaming capabilities without committing to a subscription.

## Known failure modes

- Payment not received or insufficient USDC — returns payment required or authorization error
- Invalid or missing API key — returns 401 unauthorized
- x402 payment protocol handshake failure — returns 402 with payment details
- Token already active for wallet — may return existing token or conflict error
- Network timeout during payment settlement — returns 408 or 504

## How this service works

Professional market data API for crypto derivatives, spot markets, prediction markets, Hyperliquid HyperCore data, proprietary volatility surfaces, and analytics.

## Authentication

Use an API key for authenticated REST requests:

```http
X-API-Key: your-api-key-here
```

Most data endpoints also support x402 pay-per-request without an API key.

| Resource | Path |
| --- | --- |
| OpenAPI JSON | `GET /openapi.json` |
| x402 discovery | `GET /.well-known/x402` |
| Changelog | `GET /api/v1/changelog` |
| WebSocket docs | `GET /websocket` |

## REST Surfaces

| Surface | Examples |
| --- | --- |
| Instruments | Cross-market contract reference data |
| Futures | OHLCVT, trades, tickers, orderbook, liquidations, carry |
| Perpetuals | OHLCVT, trades, funding, open interest, orderbook, liquidations |
| Options | OHLCVT, trades, Greeks, volatility, flow, dealer GEX |
| Vol Surface | Proprietary surface snapshots, slices, strikes, term structure, risk |
| Spot | OHLCVT, ticker, trades, volume, L2 orderbook, snapshots |
| Predictions | Polymarket instruments, categories, trades, ticker history |
| Hyperliquid - HyperCore | Node-derived fills, liquidations, positions, funding, TWAPs, resting orders, L2 books |
| Analytics | Realized volatility and derived metrics |

## Pagination

Paginated endpoints return the cursor at `meta.next_cursor`. Pass that value back as the `cursor` query parameter to fetch the next page.

## WebSocket Streaming

Real-time streams are documented at `/websocket`.

| Data | Channel pattern |
| --- | --- |
| Trades | `trades.{market}.{exchange}.{instrument}` |
| OHLC ticker | `ohlc.ticker.{market}.{exchange}.{instrument}.{timeframe}` |
| OHLCVT | `ohlc.vt.{market}.{exchange}.{instrument}.{timeframe}` |

Variables: `market` is one of `perpetuals`, `futures`, `options`, or `spot`; `timeframe` is one of `1m`, `5m`, `15m`, `1h`, `4h`, or `1d`.

## Quick Start

```bash
curl "https://apiv2.laevitas.ch/api/v1/futures/ohlcvt?exchange=deribit&instrument_name=BTC-PERPETUAL" \
  -H "X-API-Key: your-api-key-here"
```

## Output

Returns a JSON object containing the wallet address used for payment, the duration ('hour'), a Unix millisecond expiry timestamp, and an ISO 8601 expiry datetime string. This token is then used to authenticate WebSocket connections to Laevitas streaming endpoints.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "wallet": "0x...",
  "duration": "hour",
  "expires_at": 1730412345678,
  "expires_at_iso": "2026-04-30T18:25:45.678Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/laevitas-websocket-pass-hourly-token-5e539875/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apiv2.laevitas.ch](https://www.zero.xyz/host/apiv2.laevitas.ch/llms.txt)