> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise delivery

> Plan custom 0xArchive delivery with S3 Parquet, API and WebSocket capacity, replay, reconstruction, data-quality targets, and launch owners.

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

| Input         | Why it matters                                                                                                      |
| ------------- | ------------------------------------------------------------------------------------------------------------------- |
| Primary need  | Separates bulk historical delivery, API throughput, replay, reconstruction, security, and coverage review           |
| Venue scope   | Names Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, Lighter, or uncertain coverage                              |
| Delivery mode | Distinguishes REST/API capacity, WebSocket/replay, S3 Parquet, scheduled exports, security review, and custom terms |
| Timeline      | Sets launch, backfill, procurement, and owner expectations                                                          |
| Route set     | Turns SLA and support from generic uptime into named product behavior                                               |

## Delivery Modes

<Steps>
  <Step title="S3 Parquet bulk delivery">
    Use when files should land in a warehouse, lakehouse, research store, or partner delivery path.
  </Step>

  <Step title="Dedicated API or WebSocket capacity">
    Use when applications already know their route mix, symbol count, subscription count, replay speed, and concurrency needs.
  </Step>

  <Step title="Replay and reconstruction">
    Use when event timing, local book state, or reproducible backtests matter.
  </Step>

  <Step title="Security and procurement">
    Bring questionnaires, commercial terms, and support plan into the same route-scoped plan.
  </Step>
</Steps>

## Scope Checklist

Enterprise work should start with a route-scoped checklist, not a broad request for higher limits.

| Field             | Capture                                                                                     |
| ----------------- | ------------------------------------------------------------------------------------------- |
| Route set         | REST paths, WebSocket feeds, replay surfaces, export schemas, or Data Catalog markets       |
| Venue and symbols | Hyperliquid core, Spot, HIP-3, HIP-4, Lighter, symbol list, pair list, or market slugs      |
| Data families     | Trades, candles, L2, L3, L4, funding, open interest, liquidations, order events, or files   |
| Delivery mode     | API capacity, WebSocket capacity, replay, S3 Parquet, scheduled exports, or custom delivery |
| Time window       | Backfill range, retention expectation, replay window, and launch-date dependency            |
| Freshness target  | Latency, completeness, and SLA-style expectations for the named workflow                    |
| Consumers         | Internal research, model features, trading systems, dashboards, customers, or partners      |
| Rights review     | Internal use, derived output, redistribution, resale, or customer-facing exposure           |
| Support path      | Primary 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](/data-catalog), [Export schemas](/export-schemas), [Rate limits](/rate-limits), [Status monitoring](/status-monitoring), and [Data rights](/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.