ProvelyHermes connects to Provely through the CLI, the SDK, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. Hermes never holds the verifier credentials.
A person verified the Hermes capabilities on 2026-09-08. Agent products change monthly. Re-verify before you build.
Source: integration profile hermes · retrieved 2026-09-08
Which surfaces does Hermes use?
| Surface | Support | Detail |
|---|---|---|
| MCP server | Verify at implementation | transport stdio, http |
| CLI | Supported | Runs through the shell tool of the agent. |
| SDK | Supported | languages python, typescript |
| REST API | Supported | Any HTTP call reaches the control plane. |
Which guidance files does Hermes read?
Provely ships one Agent Skill for this host, so the agent knows to verify an outcome before it claims done. The renderer writes prompt fragment from one source. A new agent needs a profile, not core code.
Explain: each file, its path and its write mode
| Format | Path | Mode |
|---|---|---|
| prompt fragment | provely/prompt-fragment.md | fragment |
| CI gate workflow | .provely/ci/github-actions.yml | fragment |
How is a false completion claim blocked?
Guidance asks. A hook and the CI gate enforce. A host with neither still receives the verdict, and a person reads it before the work ships.
Explain: what each control does on this host
| Enforcement | Support | Detail |
|---|---|---|
| Advisory guidance | Supported | The instruction files state the rules for every agent. |
| Lifecycle hooks | Verify at implementation | No hook events stated. |
| CI gate | Supported | provely verify --wait fails the pipeline unless the verdict is VERIFIED. |
How do I connect Hermes?
Connect Hermes to Provely
- Install the CLI.Run
curl -fsSL https://provely.sh/install.sh | sh. On Windows, runirm https://provely.sh/install.ps1 | iex. Each script verifies the signed checksum before it installs the binary. - Check the MCP support of the host.The profile marks MCP as verify at implementation. When the host runs MCP, register
provely mcp. If not, use the CLI through the shell tool. - Write the guidance files.Run
provely init --agent hermes. It writesprovely/prompt-fragment.md(fragment),.provely/ci/github-actions.yml(fragment). The guidance carries one rule: a successful tool call is not completion. - Add the CI gate.Run
provely verify --wait <duration>in the pipeline. The step fails unless the verdict is VERIFIED. Exit codes: 0 VERIFIED, 2 PENDING, 3 FAILED, 4 CONTRADICTED, 5 UNVERIFIABLE, 1 error. - Report the verdict exactly as returned.VERIFIED: "The action is verified complete. Receipt: <id>." PENDING: "The action is accepted but not yet verified. Operation: <id>."
What else does the profile state?
- Checked 2026-09-08: the repository that this profile named is readable, and it holds a planning document. Its own file states "This is not a software project." It is not an agent host, and it publishes no version, no MCP surface, and no tool boundary.
- Checked 2026-09-08: the name Hermes also names a third-party agent product of another company. Nobody checked that product. Every claim below came from docs/agent-integration-plan.md section 5.6, not from the product.
- Removed 2026-09-08: the earlier profile claimed MCP support, an SDK adapter named hermes, and a refusal of a completion claim without a verdict. No adapter of that name exists in sdks/python or sdks/typescript. The claims came from docs/agent-integration-plan.md section 5.6, not from a product.
- Decide before a release: delete this profile, or name the real host and verify it. A profile for a host that nobody can check gives a reader guidance that does nothing. The generic profile already covers any unnamed host.
- The surfaces that stay true are the ones that need no host: the REST API, the CLI, and the SDKs. Any agent that runs a shell command or makes an HTTP call uses them.
Hermes keeps its action credentials, and no surface returns the verifier credentials to it. Read the credential boundary. An operation outlives the session that opened it. Read the API reference.
Which host versions does the profile cover?
>=0.1.0. The integrations team last verified the profile with no host confirmed on 2026-09-08: no Hermes agent product was found to check.