# NousResearch/hermes-agent · ZAI provider base_url config ignored; endpoint routing issues

## Open now

- 1 issue, 1 PR open on GitHub.
- #18302: \[Bug\]: ZAI/GLM provider base_url causes 429/404 errors — config ignored by 5 code paths
- PR #37816: Respect configured ZAI base URL

Most members report that the ZAI/GLM provider does not honor a configured base_url, with related pull requests proposing changes to respect it or route manual-pool entries through a resolver. One member is adjacent: it concerns \`hermes auth add\` stamping a default base_url for the kimi-coding provider, not ZAI.

## TL;DR

- 7 member(s): 1 open issue(s), 3 closed issue(s), 1 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.19`: the share of member 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.

## Open related issues

- #18302: \[Bug\]: ZAI/GLM provider base_url causes 429/404 errors — config ignored by 5 code paths

## Closed / duplicate issues

- #58071: \[Bug\] zai provider ignores config.yaml base_url and always probes endpoints in hardcoded order — standard endpoint always wins over coding endpoint
- #61563: zai manual-pool credentials always routed to metered /api/paas/v4 instead of /api/coding/paas/v4 (hermes auth add cannot override base_url)
- #68239: hermes auth add stamps registry-default base_url for kimi-coding — sk-kimi- keys paired with api.moonshot.ai/v1, instant 401

## Prior & competing PRs

- **#61575: fix(agent): route Z.AI manual-pool entries through _resolve_zai_base_url**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#37816: Respect configured ZAI base URL**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `agent/auxiliary_client.py`, `hermes_cli/auth.py`, `tests/agent/test_auxiliary_client.py`, `tests/hermes_cli/test_api_key_providers.py`
- **#58088: fix(zai): honor configured base url**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `23d3edac4e`

## Fix status

- No merged fix on record.
- Subsystem: `agent`