Skip to main content
Enterprise delivery covers buyers whose job is larger than a standard API plan or one-off Data Catalog export: custom windows, custom delivery paths, procurement review, and support expectations. Enterprise delivery is scoped around a named route set, market list, delivery path, freshness target, support model, and commercial terms. It should not be reduced to “more credits” if the real requirement is procurement, S3 delivery, replay speed, custom retention, or written SLA language.

​
Enterprise Inputs

InputWhy it matters
Primary needSeparates bulk historical delivery, API throughput, replay, reconstruction, security, and coverage review
Venue scopeNames Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, Lighter, or uncertain coverage
Delivery modeDistinguishes REST/API capacity, WebSocket/replay, S3 Parquet, scheduled exports, security review, and custom terms
TimelineSets launch, backfill, procurement, and owner expectations
Route setTurns SLA and support from generic uptime into named product behavior

​
Delivery Modes

1

S3 Parquet bulk delivery

Use when files should land in a warehouse, lakehouse, research store, or partner delivery path.
2

Dedicated API or WebSocket capacity

Use when applications already know their route mix, symbol count, subscription count, replay speed, and concurrency needs.
3

Replay and reconstruction

Use when event timing, local book state, or reproducible backtests matter.
4

Security and procurement

Bring questionnaires, commercial terms, and support plan into the same route-scoped plan.

​
Scope Checklist

Enterprise work should start with a route-scoped checklist, not a broad request for higher limits.
FieldCapture
Route setREST paths, WebSocket feeds, replay surfaces, export schemas, or Data Catalog markets
Venue and symbolsHyperliquid core, Spot, HIP-3, HIP-4, Lighter, symbol list, pair list, or market slugs
Data familiesTrades, candles, L2, L3, L4, funding, open interest, liquidations, order events, or files
Delivery modeAPI capacity, WebSocket capacity, replay, S3 Parquet, scheduled exports, or custom delivery
Time windowBackfill range, retention expectation, replay window, and launch-date dependency
Freshness targetLatency, completeness, and SLA-style expectations for the named workflow
ConsumersInternal research, model features, trading systems, dashboards, customers, or partners
Rights reviewInternal use, derived output, redistribution, resale, or customer-facing exposure
Support pathPrimary owner, escalation channel, procurement needs, and commercial review status
A request is not fully scoped if it only says “more credits”, “all markets”, or “production data”. Narrow the route set and delivery mode first, then attach limits, rights, and support expectations to that scope.

​
Delivery Documentation

Pair Enterprise work with Data catalog, Export schemas, Rate limits, Status monitoring, and Data rights. If the buyer asks for customer-facing redistribution or feed resale, do not treat an Enterprise inquiry as automatic approval; route to commercial review.

​
Acceptance Inputs

Before treating an Enterprise request as scoped, collect the route family, symbols or markets, historical window, delivery mode, freshness target, expected consumers, support owner, and launch date. Those inputs keep sales, engineering, and customer success attached to the same delivery definition.
Last modified on June 28, 2026