# How do I verify Generic agent actions with Provely?

> Connect Generic agent to Provely through the MCP server, the CLI, the SDK, the REST API. The guidance files, the hooks, and the CI gate.

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

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

A person verified the Generic agent 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 Generic agent use?

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

## Which guidance files does Generic agent read?

The renderer writes prompt fragment, tool schemas from one source. A new agent needs a profile, not core code.

| Format | Path | Mode |
| --- | --- | --- |
| prompt fragment | `provely/prompt-fragment.md` | fragment |
| tool schemas | `provely/tool-schemas.json` | fragment |
| llms.txt file | `provely/llms.txt` | fragment |
| MCP Registry entry | `provely/mcp-registry.server.json` | fragment |
| 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 | Not supported | No hook events stated. |
| CI gate | Supported | `provely verify --wait` fails the pipeline unless the verdict is VERIFIED. |

## How do I connect Generic agent?

### Connect Generic agent to Provely

1. **Install the CLI.** Run `npx provely --version`, or download the static binary.
2. **Register the MCP server.** Add the Provely server. Use `provely mcp` for stdio, or the hosted HTTP server with a bearer token. The tools are `begin`, `verify`, `status`, and `receipt`.
3. **Write the guidance files.** Run `provely init --agent generic`. It writes `provely/prompt-fragment.md` (fragment), `provely/tool-schemas.json` (fragment), `provely/llms.txt` (fragment), `provely/mcp-registry.server.json` (fragment), `.provely/ci/github-actions.yml` (fragment). The guidance carries one rule: a successful tool call is not completion.
4. **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.
5. **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: the MCP Registry server.json schema is https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json. Source: https://github.com/modelcontextprotocol/registry (docs/reference/server-json).
- An agent that makes HTTP calls uses the REST API or an SDK. An agent that runs shell commands uses the CLI. An MCP-capable host uses `provely mcp`.
- The generic profile also renders the product artifacts: llms.txt and the MCP Registry entry.

> Generic agent 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?

`>=1.0.0`. The integrations team last verified the profile with no agent host: the range names the Provely REST API /v1 (1.0.0) on 2026-09-05.

## 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)