Anthropic sk-ant-usr key misclassification fix
NousResearch/hermes-agent · cluster 133856 · agent
Data as of
Nothing open on GitHub. Fix merged in #137140. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #137140. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #137140. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where Anthropic API keys with the sk-ant-usr prefix are incorrectly classified as OAuth tokens instead of x-api-key credentials. Multiple fixes and a bug report address correcting this classification logic.
Open issues0
Open PRs0
Fixes on record
-
#137140 fix(auth): Anthropic Console keys (sk-ant-usr/svc/admin) authenticate as x-api-key, not OAuth (#133856, salvage #133874)
files:
agent/anthropic_adapter.py,agent/anthropic_credentials.py,tests/agent/test_anthropic_adapter.py,tests/agent/test_anthropic_client_auth.py,tests/agent/test_anthropic_route_oauth_identity.py
5 PRs closed without merging
From the close comments: merged via another change 3 · duplicate 1 · partial fix 1
-
#133874 fix(auth): classify sk-ant-usr* API keys as x-api-key, not OAuth · merged via another change →
82ef40a,#137140 -
#133875 fix(auth): classify Anthropic user keys as API keys · duplicate →
#133856,#133874 -
#135172 fix(anthropic): stop treating sk-ant-usr workspace API keys as OAuth tokens · merged via another change →
82ef40a,#137140 -
#135734 fix(agent): _is_oauth_token() misclassifying sk-ant-svc/usr keys as OAuth · partial fix →
d50ab2a,cf23a1a,26610b0,#101555,#123361,#107448,#75697,#113992,#80307,#135091,#133874,#135172 -
#136142 fix(anthropic): route API key families through x-api-key, not OAuth · merged via another change →
82ef40a,#137140
Closed issues · 1
- Closed#133856[Bug]: Anthropic API keys with sk-ant-usr- prefix are misclassified as OAuth tokens (Claude Code identity on a pay-per-token key)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #137140
- Closed issues
- 1
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 12 Oct 2026