MrTrades

Documentation / HyperTape

HyperTape

Product site: hypertape.io · Live room: /tape

Paid Hyperliquid L1 tape product: forever archive, REST + WebSocket access, MCP for agents, and source=hyper_tape for backtests. Same MrTrades portal identity and X-Api-Key as the rest of the stack.

Open HyperTape live room →

Naming

  • HyperTape — product name (UI, docs, marketing).
  • hypertape.io — public website and API host (same stack as app.mrtrades.com).
  • /v1/hyper_tape/* and OpenAPI tag hyper-tape — stable API identifiers (unchanged in code).

Hosts

Primary product origin is app.mrtrades.com. beta.mrtrades.com still 308s browsers to app.

# Product (three-label hosts only) https://tape.mrtrades.com https://hypertape.io https://api.hypertape.io # Current origin (always works today) https://app.mrtrades.com

All of the above reverse-proxy the same Caddy → backend/frontend stack. Paths below are relative to the host you choose.

Keys, registration & billing

  1. Open the Portal and create an account (or sign in).
  2. Under API keys, create a key. Copy it once — it is shown as mtdp_….
  3. Unlock Tier 2+ from the Portal plan tab. HyperTape REST/WS/MCP require tier ≥ 2.
  4. Send the key on every request: header X-Api-Key: mtdp_…
curl -sS https://app.mrtrades.com/v1/hyper_tape/credits \ -H "X-Api-Key: mtdp_YOUR_KEY"

Monthly list prices (USD): Tier 1 $49 · Tier 2 $99 · Tier 3 $199. Tape credits are granted on T2/T3; heavier usage will move to a dedicated HyperTape SKU (see Credits).

Credits

  • 1 credit ≈ 1 MB warm data materialized on a cache miss.
  • Sealed / already-local hours = 0 credits (download-once forever archive).
  • Monthly allotment today: T2 = 500 · T3 = 5 000 (granted once per calendar month).
  • Check balance: GET /v1/hyper_tape/credits

REST API

All routes require tier ≥ 2 unless noted.

MethodPathPurpose
GET/v1/hyper_tape/coverageSealed vs missing hours for a window
POST/v1/hyper_tape/estimateCredits to materialize misses (cache hit = 0)
POST/v1/hyper_tape/fetchPromote/materialize missing hours into archive
GET/v1/hyper_tape/tradesPaginated trade slice (HL, prefers node origin)
GET/v1/hyper_tape/creditsRemaining credits + tier

Estimate then fetch

# What do we already have? curl -sS -X POST https://app.mrtrades.com/v1/hyper_tape/estimate \ -H "X-Api-Key: mtdp_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"channel":"trades","days":3,"coins":["BTC"]}' # Materialize missing hours (local node promote first; S3 backfill later) curl -sS -X POST https://app.mrtrades.com/v1/hyper_tape/fetch \ -H "X-Api-Key: mtdp_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"channel":"trades","days":3,"coins":["BTC"],"debit":true}'

Read trades

curl -sS "https://app.mrtrades.com/v1/hyper_tape/trades?symbol=BTC-USD&days=1&limit=100" \ -H "X-Api-Key: mtdp_YOUR_KEY"

WebSocket — live restream & replay

Endpoint: wss://<host>/v1/hyper_tape/ws

First message must authenticate (no header on bare WS upgrades from some clients):

// Live fanout (filter optional) {"api_key":"mtdp_YOUR_KEY","mode":"live","coins":["BTC","ETH"]} // Historical replay from sealed/DB window {"api_key":"mtdp_YOUR_KEY","mode":"replay","coins":["BTC"], "start":"2026-07-31T00:00:00Z","end":"2026-07-31T01:00:00Z","speed":5}
  • mode=live — Redis mtdp:trades stream (includes node push when live).
  • mode=replay — ordered trades for the window; speed 1–20× (tier-capped later).
  • Events: trade, ping, replay_start, replay_end, error.

Swagger / OpenAPI

In Swagger, use Authorize and set the X-Api-Key header (scheme name follows the OpenAPI security entry for portal keys).

MCP tools (LLM / agents)

Agents are another client of the same REST APIs. Hosted (any internet LLM): https://app.mrtrades.com/mcp with header X-Api-Key — put the key in the client config, not the prompt. Local packages: services/hyper_tape_mcp/ (tape-only) and services/mrtrades_mcp (tape + strategies + gated exec).

ToolMaps to
hyper_tape_coverageGET /v1/hyper_tape/coverage
hyper_tape_estimatePOST /v1/hyper_tape/estimate
hyper_tape_fetchPOST /v1/hyper_tape/fetch
hyper_tape_creditsGET /v1/hyper_tape/credits
backtest_runGET /v1/backtest/run?source=hyper_tape
backtest_universeGET /v1/backtest/universe

Prefer the unified server when you also need Nexus/exec: services/mrtrades_mcp (stdio or Streamable HTTP). Tape-only: this package.

pip install mcp httpx export MTDP_API_BASE=https://app.mrtrades.com/v1 export MTDP_API_KEY=mtdp_YOUR_KEY # from repo: services/hyper_tape_mcp PYTHONPATH=services/hyper_tape_mcp python -m hyper_tape_mcp.server # unified (tape + Nexus + gated exec): PYTHONPATH=services/mrtrades_mcp python -m mrtrades_mcp.server PYTHONPATH=services/mrtrades_mcp python -m mrtrades_mcp.server --transport streamable-http --port 8765

Point Cursor / Claude Desktop MCP config at that stdio command. Or skip local Python and call https://app.mrtrades.com/mcp/call. Materialize still burns tape credits under the same key. Strategy tools: Strategies docs.

Microstructure viz (live room + API)

The HyperTape live room at /tape shows print flow, whale lane, OB heat, and a 60s absorption badge for the focus coin. The same metrics are available over REST (no API key required for public viz endpoints on common-universe symbols):

EndpointPurpose
GET /v1/viz/absorption60s aggressive flow vs price move (absorption bias)
GET /v1/viz/liquidity_heatmapShallow L2 size × price × time (common universe)
GET /v1/viz/flow_mapTop buyer/seller wallets (tier ≥ 2, API key)
GET /v1/viz/tape_heatPrint intensity heatmap
curl -sS "https://app.mrtrades.com/v1/viz/absorption?symbol=BTC-USD&window_sec=60"

Terminal Heat tab uses the same viz APIs for liquidity heat and flow map; absorption is shown in the HyperTape room stats strip today.

Backtest source

Event/forward-return engine with L1 provenance. source=hyper_tape requires tier ≥ 2 and uses node tape — both hl_node_trade and hl_node_fill_trade (never silently mixes public WS). Live and replay WebSocket prints include aggression when the archive has it. Fetch spends credits; cache hits do not.

curl -sS "https://app.mrtrades.com/v1/backtest/run?symbol=BTC-USD&source=hyper_tape&venue=hyperliquid&thesis=pump&interval_s=5&days=3" \ -H "X-Api-Key: mtdp_YOUR_KEY"

UI: /backtest.

Nexus relationship

Nexus is situational awareness (stats, notifications, ticker glance) — typically tier ≥ 1. HyperTape is the L1 tape data product — tier ≥ 2. Same portal account and API keys.

  • Nexus: /nexus
  • Nexus stats: GET /v1/nexus/stats (when enabled)
  • Tape does not replace Nexus; it feeds richer research/backtest and agent workflows that can sit beside Nexus awareness.

Common errors

  • 401 missing_x_api_key / invalid_api_key
  • 403 insufficient_tier — need Tier 2+ for HyperTape
  • 403 tier_required_for_hyper_tape — backtest source=hyper_tape
  • Backtest note: no_hyper_tape_data — no node-origin rows in range; run fetch / wait for live push

More