No Strix account. No SDK. No API key.

Verify without us.

Every Strix decision is Ed25519-signed against a canonical payload. The public key is served at /.well-known/strix-jwks.json (RFC 7517). Any third party — auditor, regulator, customer security team — can verify the signature with standard cryptography. Strix tooling not required.

From your terminal

One command. Four cryptographic checks.

@strixgov/verifier is a small npm package — Node 18+, zero runtime dependencies, MIT-licensed. It reconstructs each canonical payload byte-for-byte and validates the signature, hash, and chain independently. Hash valid, chain valid, signature present, signature valid — never collapsed into one boolean.

bash
# Verify a hosted evidence record (13-field canonical):
npx @strixgov/verifier 42

# Verify a Phase 3 approval artifact (9-field canonical):
npx @strixgov/verifier approval cu_artifact_abc123

# Verify the full approval quorum for a decision (chain + quorum):
npx @strixgov/verifier quorum cu_decision_xyz789

# Verify a tool-gateway receipt offline — no network, no Strix:
npx @strixgov/verifier receipt ./rcpt.json --jwks ./public-jwks.json
Expected output
@strixgov/verifier — Evidence Record
────────────────────────────────────────────────────────
  Evidence ID:       42
  Capability:        decisions.approve
  Signing key id:    strix-prod-2026-04
  Hash valid:        true
  Chain valid:       true
  Signature present: true
  Signature valid:   true
  Status:            VERIFIED

Exit codes: 0 VERIFIED, 1 FAILED, 2 ERROR (network, key not in JWKS, malformed input).

Latest releasev1.10.1 — 2026-05-18

@strixgov/verifier shipped to npm on May 15, 2026; the 1.10.x line added the visual subcommand for Visual Artifacts v1 and fixed canonical-byte handling for approval artifacts. Pin a version in production or use @latest to track the current line. MIT-licensed; the source tree lives in the platform monorepo.

Or in your browser

Paste a hash. Same checks.

evidence verification
Governance verification terminal ready.Enter any evidence hash to verify it exists in the immutable trail.
# Tip: Paste a full SHA-256 hash or minimum 8-character prefix. Try the example hash from the lifecycle demo above.
$
By ID: GET /api/proof/<id>·By hash: GET /api/public/verify?hash=<sha256>|Independently verifiable. No account required.

Try it on real production data

Copy any hash below and paste it into the verifier above — or into the CLI. These are real production evidence hashes from the live governance chain.

Live telemetry
Live governance telemetry

Total Decisions

Capabilities Active

Decision States

Bypasses

What can be verified

Every Strix trust artifact uses the same SCJ v1 canonical serialization and the same Ed25519 key set. One verifier, four independent surfaces — hosted, or fully offline.

SurfaceSubcommandNetwork
Governance evidence record<evidenceId>Public proof API
Approval artifactapproval <artifactId>Public proof API
Approval quorum (chain + quorum)quorum <decisionId>Public proof API
Tool-gateway receiptreceipt <path>Offline, local file
Tool-gateway receipt chainchain <path>Offline, local file

Public endpoints (no auth, rate-limited per IP)

GET /.well-known/strix-jwks.json

GET /api/public/proof/<evidenceId>

GET /api/public/approval-artifact/<artifactId>

GET /api/public/decisions/<decisionId>/approvals

GET /api/public/verify

Why “verify without us” matters

Most governance systems hand you a dashboard and ask you to trust it. Strix hands you a signed canonical payload and a public key. If we disappeared tomorrow, every receipt we ever produced would still be cryptographically valid against the JWKS you already archived. That is what “independently reproducible proof” actually means — and it is the difference between an audit trail and an audit story.

Want this signed proof from your own agents?

Strix sits between agent intent and real-world side effects. Capability control, fail-closed enforcement, and signed evidence on every decision — at the moment of execution.