Crypto price oracle Pyth Network has implemented a mandatory API key requirement for developers who call its Hermes price-delivery service directly. The cutover deadline passed on Aug. 26, directing traffic to an upgraded backend.
According to Pyth's migration guide, end users of protocols that already integrate the oracle do not need to take direct action. However, developers making direct calls to the service now must include an API key as a bearer token or SDK access token.
Migration Requirements and Potential Risks
Pyth noted that while route paths and response shapes remain unchanged, incomplete migrations can result in failed price-update transactions. Because the upgraded Hermes endpoint serves payloads intended for the upgraded Pyth Core contract, mismatched settings between endpoints, SDKs, and on-chain contracts can leave an application unable to verify price updates.
For Sui integrations, developers faced additional hurdles because applications reference the Pyth package by object ID. Sui builders were required to update both the client used to fetch price data and the on-chain Move package dependency by updating their Move.toml file and pointing the SuiPriceServiceConnection to the upgraded Hermes endpoint with an access token.
Scope of Impact
Data from DefiLlama mapped Pyth to 316 protocols and approximately $2.7 billion in total value secured, though this dynamic figure can include overlapping exposures. Following the deadline, there were no confirmed reports of outages, stale-price events, or loss of funds as systems adjusted to the authentication requirements.
