Skip to content

fix(providers): correct MiniMax base URL to resolve HTTP 404 errors#3546

Closed
devorun wants to merge 2 commits into
NousResearch:mainfrom
devorun:patch-15
Closed

fix(providers): correct MiniMax base URL to resolve HTTP 404 errors#3546
devorun wants to merge 2 commits into
NousResearch:mainfrom
devorun:patch-15

Conversation

@devorun

@devorun devorun commented Mar 28, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Some users are getting HTTP 404 from https://api.minimax.io/anthropic.
Root cause is unclear — may be regional, API key mismatch, or intermittent.

This PR adds a fallback to https://api.minimax.chat/v1 (OpenAI-compatible
endpoint) in auxiliary_client.py when env vars are not set, and corrects
the PROVIDER_REGISTRY default to use the OpenAI-compatible endpoint which
appears more stable.

Users can override via MINIMAX_BASE_URL in ~/.hermes/.env if they prefer
the Anthropic-compatible endpoint.

Tested by: community report in Discord showing consistent 404 on MiniMax-M2.7

Related Issue

Fixes #

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • I searched for existing PRs to make sure this isn't a duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform:

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

  • This skill is broadly useful to most users (if bundled) — see Contributing Guide
  • SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
  • No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
  • I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

@teknium1

Copy link
Copy Markdown
Contributor

The underlying issue is real — some users get nginx 404 on the /anthropic endpoint due to geographic routing. However, this PR's approach wouldn't work because runtime_provider.py auto-corrects /v1 URLs back to /anthropic (the PR didn't account for that).

Fixed in PR #3553 with a different approach: removed the auto-correction so users can override via MINIMAX_BASE_URL=https://api.minimax.chat/v1 and get chat_completions mode. The default /anthropic endpoint is unchanged for users where it works. Thanks for surfacing this!

@teknium1 teknium1 closed this Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants