# How do I verify Grok actions with Provely?

> Connect Grok 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/grok  
Last reviewed: 2026-09-05  

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

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

| Surface | Support | Detail |
| --- | --- | --- |
| [MCP server](/docs/mcp) | Verify at implementation | transport stdio, http |
| [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 Grok 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 |
| 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 Grok?

### Connect Grok to Provely

1. **Install the CLI.** Run `npx provely --version`, or download the static binary.
2. **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.
3. **Write the guidance files.** Run `provely init --agent grok`. It writes `provely/prompt-fragment.md` (fragment), `provely/tool-schemas.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 xAI SDK offers function calling. Source: https://github.com/xai-org/xai-sdk-python (README). The tool schema shape in provely/tool-schemas.json follows the OpenAI-compatible form; re-check it against https://docs.x.ai before a release.
- Give the xAI API the four function-calling tool schemas. Append the prompt fragment to the system prompt.
- Inside an MCP-capable host, the MCP server works unchanged. Verify the host at implementation. Where no MCP exists, call the CLI through the shell tool.

> Grok 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 xai-sdk 1.19.0 on 2026-09-05 (PyPI); docs.x.ai unreachable from the build host.

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