Alchemy is going all-in on Hyperliquid

We're planting a flag: Alchemy is building the most complete developer platform for Hyperliquid in the industry. HyperEVM RPC is the starting line, not the finish. Over the coming months we're shipping a full HyperCore data layer, real-time streaming, and validator-grade infrastructure. The same platform already powers more than $1T in annual transactions for Phantom, Robinhood, Stripe, Coinbase, Circle, Kinexys by J.P. Morgan, Polymarket, and many others. Now we're pointing it at the fastest growing venue onchain: perpetual futures and prediction markets.

Integrating Hyperliquid today means stitching together public endpoints, running your own indexers, and praying your data stream doesn't drop mid-liquidation. That's exactly the kind of problem Alchemy was built to solve, so the teams building the next generation of onchain trading apps—and the agents that will trade on them—can ship on infrastructure that doesn't blink.

Get your HyperEVM API key or talk to our team to help shape the HyperCore data layer.

What is Hyperliquid?

Hyperliquid is a high-performance L1 purpose-built for finance. Unlike general-purpose chains that bolt trading on top of a generic VM, Hyperliquid runs a fully onchain central limit order book (CLOB) as a first-class primitive. It's the same price-time priority matching you'd expect from a centralized exchange, but settled transparently onchain.

It's built on three tightly integrated layers:

• HyperBFT — a custom HotStuff-derived consensus protocol delivering sub-second finality and throughput measured in the hundreds of thousands of orders per second. This is what lets an onchain order book feel like a CEX.
• HyperCore — the native trading engine. Every perp and spot order, fill, funding payment, and liquidation lives directly in HyperCore state. This is the heart of the network and where the most valuable data lives.
• HyperEVM — a fully EVM-compatible execution environment that shares data with HyperCore through precompiles, so smart contracts can read live order book and account data without external oracles.

That last point is the magic. On Hyperliquid, a DeFi protocol can read a real, onchain mark price directly from the matching engine, with no oracle latency and no trust assumptions layered on top. The trade-off for builders is that the most interesting data lives in HyperCore, which doesn't behave like a standard EVM chain. Serving it well takes purpose-built infrastructure. That's the gap we're closing.

HyperEVM: the on-ramp builders already know

If you can deploy a Solidity contract, you can build on HyperEVM. It follows the Cancun spec (minus blobs), so the tooling you already use—Foundry, Hardhat, viem, ethers—works without modification. Under the hood, HyperEVM uses a dual-block design: fast, small blocks for EVM transactions and larger blocks that settle alongside HyperCore's order-book actions, all under one consensus.

For HyperEVM, Alchemy gives you what you'd expect from us on any EVM chain: reliable, low-latency JSON-RPC, the same dashboard and API keys you use for Ethereum and 100+ other networks, and our enhanced APIs for tokens, transfers, and transaction history. With hundreds of projects already building on HyperEVM, the demand for production-grade RPC is here today—and that's live now.

Follow the HyperEVM API quickstart to connect from your existing stack, or browse HyperEVM RPC endpoints and network details in the dashboard.

But EVM access alone doesn't open up Hyperliquid. The real opportunity is HyperCore.

HyperCore: the data layer we're building

HyperCore holds the data traders actually care about: every order, fill, funding payment, and liquidation. It's also where the tooling is weakest today. The network's read layer is a single Info endpoint plus a WebSocket feed: powerful, but raw. Teams that want order books, fills, funding rates, positions, and the liquidation feed at production scale end up running their own indexing, reconnection, and gap-detection logic. When markets move—which is exactly when the data matters most—that homegrown infrastructure is what breaks. Great infrastructure takes a bit more time, but that's what we're committing to for builders.

We're building HyperCore data APIs to make it our problem, not yours. Specifically, we're working toward:

• Indexed REST APIs for the queries the raw endpoint can't answer cheaply: historical fills, funding history, account positions over time, and enriched market metadata—answered in milliseconds, paginated, and backfillable.
• Real-time streaming for order book updates, trades, funding, and the liquidation feed—with multi-node redundancy and replay on reconnect, so a client restart never becomes a missed liquidation.
• One platform, one set of keys. Query HyperCore, HyperEVM, Ethereum, Solana, and Bitcoin through the same dashboard, the same metering, and the same SLAs.

This is the same playbook we ran for Solana streaming: instead of a single node that spikes or drops under load, we aggregate across multiple upstreams, deduplicate, and deliver the fastest healthy result. The stream stays steady even when individual nodes don't. We think the trading, MEV, and analytics teams on Hyperliquid deserve exactly that.

Validators: infrastructure at the base layer

Great data starts at the source. Hyperliquid secures itself through HyperBFT, where a set of validators—expanding over time as the network decentralizes—must reach a two-thirds-stake quorum to finalize blocks. Running infrastructure close to the validator set is what lets us deliver the lowest-latency, most reliable view of HyperCore state.

Alchemy intends to participate at the validator and node-operator level on Hyperliquid, the same way we operate deep infrastructure across the networks we support. Being close to consensus isn't just about decentralization. It's how we guarantee the freshness and integrity of the data we serve back to developers, and how we contribute to the long-term health of a network we're betting on.

The long game: building for traders

Hyperliquid is, at its core, where people trade. So the developers we most want to serve are the ones building for traders: market makers competing on execution latency, arbitrage and liquidation bots where milliseconds decide profitability, analytics and risk platforms that can't tolerate gaps, and the wallets and front-ends rendering real-time positions and PnL for end users.

Our long-term commitment is to be the infrastructure backbone underneath all of them. That means data that's fast enough for execution-sensitive workloads, reliable enough to trust during the most volatile windows, and complete enough that you never have to leave the platform to assemble a full picture of the market. As Hyperliquid's product surface grows—with new markets, new HyperEVM primitives, and deeper composability between the two layers—we'll grow our coverage alongside it.

This is just the start

HyperEVM RPC is live on Alchemy today. HyperCore data APIs, streaming, and validator infrastructure are what we're building next—and we want to build them with the teams who'll use them. If you're building on Hyperliquid, or want to, tell us what you need.

• Start building on HyperEVM from your Alchemy dashboard.
• Read the HyperEVM quickstart and explore the HyperEVM development platform.
• Contact our team to help shape the HyperCore data layer.

For a deeper look at how HyperEVM RPC fits into the broader provider landscape, see our guide to Hyperliquid RPC providers. We're listening.