# How do I verify pi actions with Provely?

> Connect pi to Provely through the CLI, the REST API. The guidance files, the hooks, and the CI gate. The profile was verified on 2026-09-05.

Canonical: https://provely.sh/agents/pi  
Last reviewed: 2026-09-05  

**pi connects to Provely through the CLI, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. pi never holds the verifier credentials.**

A person verified the pi capabilities on 2026-09-05. Agent products change monthly. Re-verify before you build.

Source: https://provely.sh/agents (retrieved 2026-09-05)

## Which surfaces does pi use?

| Surface | Support | Detail |
| --- | --- | --- |
| [MCP server](/docs/mcp) | Not supported | transport  |
| [CLI](/docs/cli) | Supported | Runs through the shell tool of the agent. |
| [SDK](/docs/sdk) | Not supported |  |
| [REST API](/docs/api) | Supported | Any HTTP call reaches the control plane. |

## Which guidance files does pi read?

The renderer writes AGENTS.md fragment, Agent Skills SKILL.md from one source. A new agent needs a profile, not core code.

| Format | Path | Mode |
| --- | --- | --- |
| AGENTS.md fragment | `AGENTS.md` | append |
| Agent Skills SKILL.md | `.pi/skills/provely-outcome-verification/SKILL.md` | write |
| CI gate workflow | `.provely/ci/github-actions.yml` | fragment |

## How is a false completion claim blocked?

| 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 pi?

### Connect pi to Provely

1. **Install the CLI.** Run `npx provely --version`, or download the static binary.
2. **Write the guidance files.** Run `provely init --agent pi`. It writes `AGENTS.md` (append), `.pi/skills/provely-outcome-verification/SKILL.md` (write), `.provely/ci/github-actions.yml` (fragment). The guidance carries one rule: a successful tool call is not completion.
3. **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.
4. **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-05: pi loads AGENTS.md from ~/.pi/agent, parent directories, and the current directory. pi has no built-in MCP. Source: https://github.com/badlogic/pi-mono (packages/coding-agent/README.md).
- Verified 2026-09-05: pi reads skills from .pi/skills, .agents/skills, ~/.pi/agent/skills, and ~/.agents/skills. Same source.
- pi extensions are TypeScript modules with event handlers and custom tools. An extension can wrap the SDK and can block a turn. Verify the event names at implementation before you build a hook.
- The CLI surface works through the pi tool execution.

> pi keeps its action credentials, and no surface returns the verifier credentials to it. Read [the credential boundary](/docs/security). An operation outlives the session that opened it. Read [the API reference](/docs/api).

### Which host versions does the profile cover?

`>=0.80.0`. The integrations team last verified the profile with 0.85.0 on 2026-09-05 (npm @earendil-works/pi-coding-agent).

## Read next

- [Verify Claude Code actions](https://provely.sh/agents/claude-code)
- [Verify Codex actions](https://provely.sh/agents/codex)
- [Verify Resend actions](https://provely.sh/verify/resend)
- [See every agent integration](https://provely.sh/agents)
- [Read the MCP server reference](https://provely.sh/docs/mcp)
- [Read the credential boundary](https://provely.sh/docs/security)