Cowrie Research

pyth-pro

4 min read

Pyth Pro

  • Name: Pyth Pro
  • URL: https://docs.pyth.network/price-feeds/pro
  • Category: low-latency oracle-distribution layer / market-data subscription service / signed-payload delivery middleware
  • Tags: solana-ecosystem
  • Summary: Pyth Pro is Pyth’s low-latency market-data distribution product, not the same thing as the parent network’s public oracle rail. The important layer is the gated delivery stack: API keys, distributor endpoints, channel entitlements, payload formats, and signed data that can later be verified onchain.
  • What it does:
    • Provides subscription access to real-time market-data streams under the current Pyth Pro brand, which the docs explicitly note was previously known as Pyth Lazer
    • Delivers price updates over authenticated websocket endpoints using API keys obtained through Pyth Terminal
    • Lets subscribers choose feed IDs, requested properties, binary formats, and delivery channels such as real_time, fixed_rate@1ms, fixed_rate@50ms, fixed_rate@200ms, and fixed_rate@1000ms
    • Returns structured parsed payloads plus signed binary payloads for EVM, Solana, and other supported verification formats
    • Exposes SDKs, examples, and contract-side parsing libraries so applications can receive data offchain and submit signed updates into onchain verification flows
    • Sells distinct commercial tiers, including crypto-only and broader Pro access, with different coverage, latency, and licensing / redistribution rights
  • Key claims:
    • The official docs say Pyth Pro “was previously known as Pyth Lazer” and describe it as a customizable, enterprise-grade price-data offering delivered directly from first-party publishers.
    • The most important analytical reason to keep Pyth Pro separate from the parent Pyth Network entry is that its docs expose a distinct distribution-control layer: authenticated websocket access, API-key management, fixed endpoint URLs, and mandatory connection to multiple operator-provided endpoints for redundancy during deployments.
    • The subscription docs show that control does not sit only in publisher sourcing. Subscribers must choose which feeds, which properties, which signature formats, and which latency channel they want, while feed-level minimum-channel rules determine which update frequencies are actually available.
    • The payload reference makes another useful split explicit: the same stream can serve parsed offchain values plus signed binary payloads tailored to different execution environments such as EVM and Solana. That turns Pyth Pro into delivery middleware between data publication and chain-specific verification rather than just a generic faster oracle endpoint.
    • The pricing page is unusually revealing because it introduces explicit commercial and legal policy surfaces — update-frequency tiers, asset-class coverage, display versus non-display rights, limited redistribution rights, and the note that data is distributed through authorized Pyth Data Distributors. That makes the rent surface easier to locate than in many oracle projects that market decentralization while hiding distributor control.
    • The EVM integration docs reinforce that the low-latency stream is not self-sufficient onchain: consumers still need backend or frontend subscription infrastructure, must pass updates into contracts, and must pay a verification fee to parse and verify signed updates. This cleanly separates offchain delivery from onchain verification.
    • Pyth Pro clears the corpus bar because keeping it folded only into Pyth Network would flatten away a distinct low-latency oracle-distribution mechanism where access control, routing endpoints, payload-format policy, and licensing rights matter as much as publisher set or aggregation method.
  • Whitepaper: No canonical standalone Pyth Pro / Pyth Lazer whitepaper surfaced in this pass. The strongest primary materials were the official Pyth Pro docs, subscription and payload-reference pages, pricing page, EVM integration docs, and the public Pyth Pro repository collected in ../whitepapers/pyth-pro-primary-sources-2026-05-14.md.
  • Sources:

Internal linkages

Control surface

  • Practical authority sits in API access, distributor routing, channel and update-frequency entitlements, payload-format support, and the offchain infrastructure needed to carry signed updates into contracts.

  • Signed data does not make this neutral plumbing. The sticky layer is who gets the stream, at what latency, through which endpoints, on what commercial terms.

  • Read Pyth Pro as oracle-delivery middleware, not as the same thing as the parent oracle network.

  • Last reviewed: 2026-06-03 UTC

Graph View

Backlinks