Cairn

OpenRouter budget-limit 403 misclassified as auth error

NousResearch/hermes-agent · cluster 107166

Data as of

Nothing open on GitHub. Fix merged in #113970. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #113970. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #113970. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where OpenRouter's monthly budget-limit 403 response was incorrectly classified as an authentication error, preventing auxiliary fallback from triggering. The members address detection and classification fixes to route these errors to billing handling instead.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #113970 fix(aux): OpenRouter budget-limit 403 falls back, quarantine logs name the real reason, vision fallback skips text-only models (#107166, #64144, #108349, salvage #107173 #64146 #108366)

    merged to main

    files: agent/auxiliary_client.py, agent/error_classifier.py, tests/agent/test_auxiliary_client.py, tests/agent/test_auxiliary_error_classification.py

3 PRs closed without merging

From the close comments: duplicate 2 · done elsewhere 1

  • #107173 fix(agent): classify OpenRouter org budget-limit 403 as billing · done elsewhere → a1238ad, #113970
  • #107179 fix(auxiliary): recognize OpenRouter budget limits · duplicate → #107173, #107166
  • #107210 fix(agent): add "budget limit" to billing detection patterns (#107166) · duplicate → #107173, #107166
Closed issues · 1
  • Closed#107166[Bug]: OpenRouter org "Budget limit exceeded (monthly limit)" 403 is misclassified as auth, and auxiliary fallback never triggers (keyword-list divergence)
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs
#113970
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
17 Sep 2026

For your agent

The same facts, typed.

cluster/107166.json
cluster/107166.md