What One Key Returns
Where Hydromancer Fits
0xArchive sells bounded market-data routes, not builder-platform operations; that operational layer is Hydromancer’s. Its site lists a builder REST API with batch endpoints such asbuilderFillsByTime and builderLiquidations that query 1,000+ wallets at once, WebSocket streaming for fills and orders, L2 and L4 order-book streaming with address visibility, and Reservoir, a free Parquet-on-S3 archive of Hyperliquid historical data. Paid tiers run 2,500 a month with an uptime SLA, and more than 80 apps build on it. When the job is builder-platform tooling, builder-fill analytics, or a free S3 corpus to explore, Hydromancer owns that job, and 0xArchive is not the right fit for it; this API is the archive layer underneath, the records rather than the platform.
Hydromancer covers one venue. When the same job also needs Lighter, or needs a bounded REST route with a stated historical window instead of a bucket to crawl, the decision moves here.