verdict status
Read server health and whether a policy is loaded.
Runs against the selected server connection. Effects: read server state.
Arguments and flags
Section titled “Arguments and flags”| Argument | Type | Required | Default | Description |
|---|---|---|---|---|
--json | boolean | no | false | Output as JSON |
--endpoint | string | no | No parser default | Instance base URL, including any subpath (env: VERDICT_HOST, fallback: http://localhost:4891) |
--host | string | no | No parser default | Alias for —endpoint |
--api-key | string | no | No parser default | API key (env: VERDICT_API_KEY takes precedence) |
--profile | string | no | No parser default | Stored profile (env: VERDICT_PROFILE) |
--local | boolean | no | false | Use http://localhost:4891 without stored or environment credentials |
--help (-h) shows command help without executing the command. Boolean flags support --no-<flag>. Defaults stated in descriptions may be resolved by the handler or configuration rather than the argument parser.
Command arguments and flags; stdin is unsupported.
File input: unsupported. Standard input: unsupported.
Result
Section titled “Result”{ "kind": "json-schema", "schema": { "type": "object", "required": [ "status" ], "additionalProperties": true, "properties": { "status": { "type": "string" }, "policy_loaded": { "type": "boolean", "nullable": true } } }}By default, the command renders human-readable records. --json writes one JSON result to stdout. Operational failures use status 1; JSON failures contain an error object with code and message. See shared output semantics.
Exit status
Section titled “Exit status”- 0: the health response was received and decoded.
- 1: the health request could not connect; JSON output contains status: unreachable.
Argument, I/O, and other failures handled by the CLI runner use status 1.
Examples
Section titled “Examples”verdict status --local --json