> For the complete documentation index, see [llms.txt](https://docs.scrt.network/secret-network-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/verifying-a-secretvm/secretvm-verify-sdk/cli-reference.md).

# CLI Reference

```bash
secretvm-verify <command> [options]
```

## Commands

| Command                                               | Description                                       |
| ----------------------------------------------------- | ------------------------------------------------- |
| `--secretvm <url>`                                    | End-to-end SecretVM verification                  |
| `--cpu <file\|--vm url>`                              | Verify a CPU quote (auto-detect TDX vs SEV-SNP)   |
| `--tdx <file\|--vm url>`                              | Verify an Intel TDX quote                         |
| `--sev <file\|--vm url>`                              | Verify an AMD SEV-SNP report                      |
| `--gpu <file\|--vm url>`                              | Verify an NVIDIA GPU attestation                  |
| `--verify-workload <file\|--vm url> --compose <file>` | Verify a quote against a docker-compose           |
| `--resolve-version <file\|--vm url>`                  | Identify which SecretVM template produced a quote |
| `--check-agent <id> --chain <name>`                   | Resolve and verify an ERC-8004 agent              |
| `--compose <file\|--vm url>`                          | Print the docker-compose.yaml to stdout           |

## Options

| Option             | Description                                        |
| ------------------ | -------------------------------------------------- |
| `--enforce-gpu`    | Require a verifiable GPU; fail CPU-only VMs        |
| `--json \| --raw`  | Structured output                                  |
| `--strict`         | Disable stale-cache fallback on AMD KDS failure    |
| `--proof-of-cloud` | Run the SCRT Labs proof-of-cloud check             |
| `--reload-amd-kds` | Bypass the local AMD KDS cache                     |
| `--show-compose`   | Print the verified docker-compose after the checks |
| `--verbose, -v`    | Pretty-print parsed report fields                  |

A bare URL defaults to `--secretvm`:

```bash
secretvm-verify my-vm.vm.scrtlabs.com
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scrt.network/secret-network-documentation/secretvm-confidential-virtual-machines/verifying-a-secretvm/secretvm-verify-sdk/cli-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.