Public Evidence

What we can actually prove.

Every claim below carries its evidence state. VERIFIED means reproducible with real hardware/code; PILOT means real internal evidence, labelled as such.

A real signed evidence payload, sample data

run.evidence.json · SAMPLEok

{"payload_version": "witnio-run-evidence-v1",
"run_id": "run_8f21c4a0",
"check_id": "chk_access-monitor-01",
"status": "ok",
"ran_at": "2026-09-23T08:14:02Z",
"latency_ms": 412,
"tenant_id": "tn_sample",
"device_id": "dev_SAMPLE00001",
"network": { egress: "wifi" },
"duration_ms": 1830,
"is_backtest": false,
"workflow_version": "v3.2.0",
"evidence": [
{ path: "screens/step-01.png", sha256: "a3f1…SAMPLE…9c2e", bytes: 184203 },
{ path: "logcat/session.log", sha256: "b7d4…SAMPLE…41af", bytes: 9412 },
],
"signature": "MEUCIQDsample…SIGNATURE……",
"key_id": "witnio-run-ed25519-2026-09",
"algorithm": "Ed25519",
"canonicalization": "RFC8785-JCS",
"signed_at": "2026-09-23T08:14:03Z"
}

sha256 e41c9a7d2b5f…3c6081

Verify →

Verify it yourself

3 steps to check any evidence file

The same 2 public endpoints our own backend uses internally — no account needed.

1. Get the published signing keys

Fetch the active Ed25519 public key you will check the signature against.

bash

curl -sS https://api.witnio.com/api/v1/evidence/keys

2. Send the manifest, signature and key_id

POST the exact manifest JSON, its base64 signature, and the key_id to the public verifier.

bash

curl -sS https://api.witnio.com/api/v1/public/evidence/verify \
  -H "Content-Type: application/json" \
  -d '{
    "manifest": { "run_id": "SAMPLE", "product_code": "witnio_monitor", "status": "ok" },
    "signature": "SAMPLE-base64-signature",
    "key_id": "witnio-run-ed25519-2026-09"
  }'

3. Read the verdict

A JSON body with "valid": true/false — never a partial or ambiguous result.

json

{ "valid": true, "manifest_sha256": "e41c9a7d2b5f80…SAMPLE…3c6081" }

Public claims

What we can actually prove

Loading evidence...

Back to pricing