ZenGo MiniMax models return 401 Missing API key on all requests

[yowmamasita]

Summary

Both zgo@minimax-m2.5 and zgo@minimax-m2.7 return HTTP 401 "Missing API key." on every request — including simple prompts and probe. The API key never reaches the MiniMax provider.

This is a separate root cause from the Kimi reasoning_content bug tracked in #110.

Environment

• claudish v7.0.3
• Models: zgo@minimax-m2.5, zgo@minimax-m2.7

Reproduction

claudish --probe zgo@minimax-m2.5
# → ⊗ auth 401: Missing API key.

claudish --model zgo@minimax-m2.5 -p "say hello"
# → 401 {"type":"error","error":{"type":"AuthError","message":"Missing API key."}}

Both models fail identically.

Probe output

zgo@minimax-m2.5
  # │ Provider        │ Model Spec                       │ Status
  1 │ opencode-zen-go │ opencode-zen-go@zgo@minimax-m2.5 │ ⊗ auth 401
      └ Missing API key.

zgo@minimax-m2.7
  # │ Provider        │ Model Spec                       │ Status
  1 │ opencode-zen-go │ opencode-zen-go@zgo@minimax-m2.7 │ ⊗ auth 401
      └ Missing API key.

Debug log

Debug logs show repeated 401s with no successful auth attempt. The error body is consistently:

{"type":"error","error":{"type":"AuthError","message":"Missing API key."}}

Context

Other ZenGo models using the same opencode-zen-go endpoint authenticate fine (GLM, MIMO, Qwen, Kimi all work). This suggests the issue is specific to how Zen Go forwards credentials when the underlying provider is MiniMax — possibly a transport/header wiring issue in providers/transport/ for MiniMax targets.

See full compatibility matrix in #110 (comment).

[claudish-bot]

@yowmamasita Reproduced and traced it — this is an auth scheme mismatch specific to the MiniMax branch of the ZenGo profile.

What's happening:

• openCodeZenProfile routes MiniMax models through AnthropicProviderTransport (provider-profiles.ts:194), while GLM/Qwen/Kimi go through OpenAIProviderTransport which hardcodes Authorization: Bearer
• AnthropicProviderTransport.getHeaders() checks provider.authScheme — if it's not "bearer", it falls back to x-api-key (anthropic-compat.ts:41-45)
• The opencode-zen-go provider definition (provider-definitions.ts:431-450) doesn't set authScheme, so MiniMax requests go out with x-api-key — which ZenGo's Anthropic endpoint rejects as "Missing API key"

Fix is a one-liner: add authScheme: "bearer" to the opencode-zen-go definition. I'll push a patch.