Personal API key shows Active but token endpoint returns 401 (3 keys, Garmin's own client)

My Personal API key shows as Active on connect.garmin.com (Settings > Personal API Key), but every token request returns HTTP 401 Unauthorized with an empty body.

What I've tried:
- Three separate keys (created Oct 30, Oct 31 and Nov 1 UTC), each copied with the page's copy button. All three rejected the same way.
- Garmin's official client, gc-personal 1.0.0 (refresh-token): 401.
- Plain curl exactly as shown on developer.garmin.com/gc-developer-program/personal/personal-api:
  POST personal.connectapi.garmin.com/.../token
  Authorization: ApiKey <key>
  Result: 401, content-length 0, www-authenticate: Bearer.
- Two different networks (home and phone cellular hotspot): same result.
- The key is 128 ASCII characters starting with GCDC_, with no stray whitespace.
- Account is on connect.garmin.com (US).

Others report this same request returning 200, so it looks specific to my account. Is there an account setting or condition that prevents Personal API keys from working, or can someone on the team check my account?