$PYTH SDK onboarding gap: the official hermes-client README still teaches the keyless setup that now returns 401.

What I tried (4 Oct 2026): copied the Quickstart from pyth-crosschain apps/hermes/client/js/README.md — new HermesClient("https://hermes.pyth.network", {}) — and also hit the REST endpoint directly:

curl -i "https://hermes.pyth.network/v2/updates/price/latest?ids[]=0xef0d8b6f...b56d"

-> HTTP 401, body "unauthorized".

The docs banner explains it (Hermes requires an API key since the Aug 26, 2026 Pyth Core upgrade), but the README's Quickstart (line 26), the example-runner command, and the "Pyth offers a free public endpoint at hermes.pyth.network" line (line 93) never mention auth. The SDK already supports keys: HermesClientConfig has accessToken, sent as Authorization: Bearer (and as ACCESS_TOKEN for SSE/WebSocket) in hermes-client@3.1.0.

Suggestion: update the Quickstart to new HermesClient(endpoint, { accessToken: process.env.PYTH_API_KEY }), add the key-signup link beside it, and fix the "free public endpoint" sentence + example command. Right now a builder copying the README hits a 401 that looks like an outage.

Question: should SDK users switch the base URL to the upgraded pyth.dourolabs.app/hermes, or does hermes.pyth.network stay valid once a key is set?