powertokens platform, the stable path is the platform /v1/chat/completions compatible endpoint.
The platform /v1/messages Anthropic Messages endpoint is available, but Hermes Agent provider routing differs by version. In Hermes Agent v0.10.0, the main chat path may still request /chat/completions even when api_mode: anthropic_messages is configured, and may normalize glm-5.2 to glm-5-2. This page treats anthropic_messages as a version-gated setup direction, not as a stable Hermes Agent promise.
If you need to choose the endpoint first, see Text model protocols and endpoints.
Choose a path
OpenAI-compatible endpoint
Start Hermes model setup:
If your Hermes version asks for the full chat completions endpoint, use:
anthropic_messages version check
Only useanthropic_messages when your Hermes version is confirmed to send the request to POST /v1/messages. Adapt this field shape to the config format used by your Hermes version:
https://baze-api.powerbuyin.top/v1/messages. If the request still lands on /chat/completions, do not treat this path as a stable Hermes Agent setup.
Recommended models
Recommended Anthropic tool-workflow model IDs:
Verify the OpenAI-compatible path
Verify the anthropic_messages path
Boundaries
- The Hermes custom endpoint path reliably covers
/v1/chat/completions; it does not prove the main chat path is using Anthropic Messages. api_mode: anthropic_messagesshould only be used when the current Hermes version is verified to request/v1/messages.- Tool execution, terminal control, long context, caching, and streaming should be validated with real Hermes tasks.
- If the
anthropic_messagespath is unstable in real tasks, switch to the OpenAI-compatible endpoint and keep the failed request id. - Do not copy MiniMax upstream-only fields into platform examples; this page describes the public unified API contract.