Quickstart, CLI
The verdifax-cli binary is a local pipeline test harness
in the private orchestrator repository. It runs the pipeline
in-process; it does not call the hosted API.
Install
verdifax-cli is built from the orchestrator source, and the
orchestrator source repository is not public, so there is no public
clone or download for this binary today. The supported path is the
hosted API at https://api.verdifax.com, called directly with
curl or through an official SDK
(Python, Go,
Node).
The command-line tool that is public today is the verifier,
verdifax-verify, from
github.com/Verdifax/verdifax-verify.
It checks sealed audit bundles rather than creating attestations:
go install github.com/Verdifax/verdifax-verify@latest
It requires Go 1.27 or later; prebuilt binaries are on its releases page. Use v0.14.5 or later; v0.12.0 accepts case-variant duplicate JSON keys, and earlier releases accept entries logged by any key and report records from run 240 on as failed. See Verify for usage.
What it does
verdifax-cli is only available to holders of the private orchestrator
source. It reads one JSON input, runs the pipeline in-process with mock
adapters for DOG, ZKSP, proof and state binding, the registry and DLA
(the ledger is chosen by VERDIFAX_LEDGER_MODE: mock by default,
rekor or airgap), and prints a banner, the input fields, a per-stage
table and the manifest hash. It does not call https://api.verdifax.com,
takes no API key, and its output is a local test run, not a hosted
sealed record.
verdifax-cli <input.json>
verdifax-cli --file <input.json>
verdifax-cli --inline '{"payload_text":"hello","program_id":"aaa...","route_id":"r","registry_record_hash":"bbb..."}'
verdifax-cli --demo
The input JSON carries payload_text (or payload), program_id,
route_id and registry_record_hash. --demo uses a built-in sample
input. Exit code is 0 when every stage passes and 1 on a stage
failure or bad input.
To create hosted attestations from a shell script or CI pipeline, call the API with curl or an SDK instead.