Developer workflow connector
Hermes Agent connector for governed AI agent access
Connect the native Hermes Agent HTTP API without exposing its API key to the caller.
Direct answer
OneQuery supports Hermes Agent for governed agent access.
Teams use the Hermes Agent connector to give AI agents bounded source API calls for endpoint-specific context while OneQuery keeps credentials centralized, limits access to approved sources, and preserves audit logs for review.
Agent workflow
What this connector enables
Hermes Agent becomes an approved OneQuery source instead of a secret copied into an agent prompt, shell session, or model tool. The agent receives a governed access path, and the source credentials stay behind OneQuery.
- Use bounded source API calls for endpoint-specific context for developer workflow context.
- Keep Hermes Agent credentials centralized and out of agent runtimes.
- Review agent access through OneQuery audit history instead of reconstructing direct service usage.
Setup checklist
Prepare the Hermes Agent connection
Use hermes credentials and connect the source through the Dashboard and CLI. Keep credentials scoped to the data the agent is allowed to read.
- Enable the Hermes Agent API server with `API_SERVER_ENABLED=true` and a strong `API_SERVER_KEY`.
- Expose the local Hermes API server through a secure HTTPS tunnel or private network endpoint reachable from OneQuery.
- Set `apiBaseUrl` to the Hermes API origin, for example a Cloudflare Tunnel URL.
- Copy the Hermes `API_SERVER_KEY` into `apiKey`.
- Call native paths such as `/v1/models`, `/v1/responses`, `/v1/runs`, `/api/sessions`, and `/api/jobs` through the Source API.
FAQ
Hermes Agent connector questions
What is the OneQuery Hermes Agent connector?
The OneQuery Hermes Agent connector makes developer workflow context from Hermes Agent available to AI agents through bounded source API calls for endpoint-specific context. Connect the native Hermes Agent HTTP API without exposing its API key to the caller.
How do AI agents access Hermes Agent through OneQuery?
Agents call OneQuery instead of receiving raw Hermes Agent credentials. OneQuery keeps credentials centralized, applies source boundaries, and records access in audit logs while exposing bounded source API calls for endpoint-specific context.
How do I set up the Hermes Agent connector?
Prepare hermes credentials and connect Hermes Agent from the OneQuery dashboard or CLI. Start with this setup step: Enable the Hermes Agent API server with `API_SERVER_ENABLED=true` and a strong `API_SERVER_KEY`.