OpenClaw connects to Provely through the MCP server, the CLI, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. OpenClaw never holds the verifier credentials.
A person verified the OpenClaw capabilities on 2026-09-08. Agent products change monthly. Re-verify before you build.
Source: integration profile openclaw · retrieved 2026-09-08
Which surfaces does OpenClaw use?
| Surface | Support | Detail |
|---|---|---|
| MCP server | Supported | transport stdio, http |
| CLI | Supported | Runs through the shell tool of the agent. |
| SDK | Not supported | |
| REST API | Supported | Any HTTP call reaches the control plane. |
Which guidance files does OpenClaw read?
Provely ships one Agent Skill for this host, so the agent knows to verify an outcome before it claims done. The renderer writes Agent Skills SKILL.md from one source. A new agent needs a profile, not core code.
Explain: each file, its path and its write mode
| Format | Path | Mode |
|---|---|---|
| Agent Skills SKILL.md | skills/provely-outcome-verification/SKILL.md | write |
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 | Not stated | provely verify --wait fails the pipeline unless the verdict is VERIFIED. |
How do I connect OpenClaw?
Connect OpenClaw 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. - Register the MCP server.Add the Provely server. Use
provely mcpfor stdio, or the hosted HTTP server with a bearer token. The tools arebegin,verify,status, andreceipt. - Write the guidance files.Run
provely init --agent openclaw. It writesskills/provely-outcome-verification/SKILL.md(write). The guidance carries one rule: a successful tool call is not completion. - 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?
- Verified 2026-09-08: OpenClaw reads AgentSkills SKILL.md files. It reads <workspace>/skills first, then <workspace>/.agents/skills, then ~/.agents/skills, then the managed state directory. Source: https://github.com/openclaw/openclaw (docs/concepts/agent-workspace.md).
- Write the skill into the agent workspace, not into a code repository. The default workspace is ~/.openclaw/workspace. OpenClaw also reads AGENTS.md of that workspace in every session.
- Verified 2026-09-08: OpenClaw supports MCP under mcp.servers with the transports stdio, streamable-http, and sse. A remote server takes headers with Authorization, or auth "oauth" with
openclaw mcp login. Source: docs/tools/mcp.md and docs/cli/mcp.md. - Corrected 2026-09-08: the earlier note said OpenClaw has no lifecycle hook. That was wrong. A plugin registers api.on("before_tool_call") and api.on("before_agent_run"), and both can block. Source: docs/plugins/hooks.md.
- We ship no OpenClaw plugin, so hooks stay verify_at_implementation and the rendered skill states that it is advisory. Do not raise this to yes before a plugin exists in this repository.
- The inbound hooks.* webhooks start an agent run. They are not an interception point. OpenClaw cron jobs re-check a PENDING operation with
provely status <operation_id>. - OpenClaw runs messaging, purchases, and device control. It is not a repository agent, so the CI gate and the scanner do not apply.
OpenClaw 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?
>=2026.9.0. The integrations team last verified the profile with 2026.9.3 of 2026-09-08 on 2026-09-08 (npm openclaw).