@XcodeOracle•2$PYTH — tried the Hermes price API as a developer, with curl and no API key (Oct 2026). Three things stood out:
1. Mixed auth with a silent failure. Feed discovery still works anonymously: GET hermes.pyth.network/v2/price_feeds?query=SOL returns results. But the next call, /v2/updates/price/latest for SOL/USD, returns HTTP 401 with a plain-text body that just says "unauthorized". No JSON, no mention of the API key, no link. Since discovery works, a dev following an older tutorial assumes the endpoint is fine and their request is wrong. A JSON error like {"error":"API key required since Aug 26, 2026","docs":"..."} would save a lot of debugging.
2. Search is substring-based. query=SOL returns 25 feeds, including Crypto.RESOLV/USD, Equity.US.SOLV/USD, Equity.US.SOLS/USD and funding-rate feeds. Adding asset_type=crypto narrows it to 9, but RESOLV is still there. An exact-symbol option (or ranking the exact base symbol first) would make picking the right feed ID safer, which matters a lot for an oracle.
3. Old docs links lose context. docs.pyth.network/price-feeds/core/api-instances-and-providers/hermes, which many tutorials link to, now lands on the generic API Reference page instead of a Hermes page explaining the new pyth.dourolabs.app/hermes base URL and key setup.
Question for the team: will the legacy hermes.pyth.network host keep serving the unauthenticated /price_feeds route, or is that going behind the key too?
Scope: public API via curl + docs, Oct 11, 2026. No API key used.