Repository navigation
Compatibility issue with Hermes Gateway: Missing /api/auth/status endpoint #6
Description
Description:
I am trying to use Hermex-android with a standard Hermes Gateway instance (running via Docker). While the connection seems to be partially established, the app fails to connect because it expects an /api/auth/status endpoint which does not exist in the Hermes Gateway API specification.
Logs/Error:
The application sends the following requests which result in 404 errors:
GET /api/auth/status HTTP/1.1 -> 404 Not Found
However, the standard OpenAI-compatible API is working perfectly on the same gateway:
curl http://<GATEWAY_IP>:8642/v1/chat/completions
-H "Authorization: Bearer "
-H "Content-Type: application/json"
-d '{"model": "hermes-agent", "messages": [{"role": "user", "content": "Hello!"}]}'
The above curl command returns a successful response from the agent.
Expected Behavior:
The app should rely on standard OpenAI-compatible endpoints (e.g., /v1/chat/completions) or allow users to point to the /v1 base URL without requiring proprietary auth endpoints.
Environment:
Hermex-android version: latest
Hermes Gateway version: 0.18.0
Server OS: Unraid/Docker container
Additional context:
It seems the app is hardcoded to check for proprietary auth routes. Adding support for standard OpenAI API compatibility (without enforcing /api/auth/status) would resolve this connectivity issue.
Activity
nesquena commentedon Jul 7, 2026
Just like Hermex for iOS, this app is part of a unified ecosystem using the bridge API here https://get-hermes.ai/api-docs/ that allows clients to easily interact with Hermes
So in other words, you would want to setup that API for this to connect to explained here https://hermexapp.com/#setup
ComputerByte commentedon Jul 8, 2026
Thanks for the report — this is valid.
Hermex Android currently targets the full Hermex/Hermes app-server API, not a Gateway-only/OpenAI-compatible endpoint. That’s why the app checks /api/auth/status; a plain Gateway instance may expose /v1/chat/completions but not the app-level auth/session routes Android currently depends on.
I’m going to track Gateway-only support as a post-1.0 compatibility feature rather than block the 1.0 RC on it. For 1.0, I’ll make sure the README/error messaging is clearer about requiring the full Hermex/Hermes server API.
Leaving this open for 1.1+ Gateway mode.