verdict fact add
Insert directly stored facts from a predicate literal or separate terms.
Runs against the selected server connection. Effects: mutate stored facts.
Arguments and flags
Section titled “Arguments and flags”| Argument | Type | Required | Default | Description |
|---|---|---|---|---|
<predicate> | positional | yes | No parser default | Predicate name or literal (e.g. role or ‘role(User:alice, “admin”)’) |
--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 |
--json | boolean | no | false | Output as JSON |
--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.
A predicate literal or a predicate name followed by separate terms.
File input: unsupported. Standard input: unsupported. The predicate positional accepts additional terms or paths.
Result
Section titled “Result”{ "kind": "json-schema", "schema": { "type": "object", "required": [ "completed" ], "additionalProperties": false, "properties": { "completed": { "type": "boolean" } } }}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 command completed its operation.
Argument, I/O, and other failures handled by the CLI runner use status 1.
Examples
Section titled “Examples”verdict fact add 'role(User:alice, "admin")' --json