Pyth Pro

Pro is the subscription tier of Pyth. Where Pyth Core publishes every 400 milliseconds and is free to read on-chain, Pro pushes updates roughly every millisecond over a paid subscription. If you build a perpetual exchange, an options vault, or any on-chain product that competes with off-chain venues for execution quality, this is the feed you want. Pro was previously known as Lazer.

What you actually get

• ~1ms update cadence. Two to three orders of magnitude faster than Core. The mark moves before your matching engine does.
• Same publisher set. Pro reuses the same 100+ institutional publishers feeding Core. You are getting the same data, sooner.
• Push delivery. A persistent WebSocket stream carries signed updates as they happen. No polling.
• Multi-channel access. Updates available as on-chain pull updates, off-chain WebSocket, and REST. Pick whichever fits your stack.
• Commercial wrapper. SLAs, support, and a contract with the Pyth Data Association. Required for many tradfi firms before they can take a dependency.

When Pro pays off

• Perpetual futures. Funding-rate skew and liquidation engines need fresh marks. 400ms is fine for funding accruals. 1ms is what kills toxic flow.
• On-chain market-makers. Quote-then-cancel strategies need a fast mark to avoid getting picked off.
• Options pricing. Greeks shift fast on liquid underlying. Pro is the only on-chain feed fast enough to keep an AMM book honest.
• Cross-venue arbitrage. If you settle on-chain and hedge on a centralized venue, Pro narrows the latency gap that arbitrageurs would otherwise eat.
• Institutional desks. Banks, market-makers, asset managers consuming feeds off-chain — Pro packages the same data with the contractual guarantees their compliance teams require.

How integration looks

You open a WebSocket to the Pro service, authenticate with your subscription key, subscribe to the feeds you care about, and receive signed updates as they arrive. On the contract side you accept a Pro update (a slightly different message format from Core updates) and verify it against the Pro trusted signer set.

Most teams shape it like this:

1. A keeper service holds the Pro WebSocket connection and pulls updates locally.
2. When a user trade lands in the mempool, the keeper signs and posts the latest update in front of it as a bundle (using a relayer like Flashbots or Express Relay).
3. The trade then settles against a price that is at most one millisecond old.

Trade-offs

Pro is not a drop-in replacement for Core. The differences are real:

• It costs money. You pay for the speed and the SLA.
• It needs infrastructure. A WebSocket consumer and a sequencing layer is more work than a single updatePriceFeeds call.
• Smaller feed catalog. Pro focuses on markets where speed matters — majors, top-100 crypto, large-cap equities, FX. Long-tail feeds stay on Core.

For most teams the right architecture is Pro for the active mark on top markets, and Core for everything else.