Skip to main content
This page documents the 200 response from GET /v1/verdict/{requestId}. The API returns a projection of assessment schema 10, not the full edge assessment.

Top-level fields

string
required
Tenant response contract version. The current value is "1".
string
required
Raw nonce stored by the control plane. It has no req_ prefix.
string
required
contradicted, refused, disputed, uncontradicted, or insufficient.
boolean
required
Whether the categorical ruling rule was met. It is not a probability or a tenant action.
string | null
required
sensor-gap, awaiting-return, or no-return for an insufficient assessment. Otherwise null.
boolean
required
true when verdict is refused.
string | null
required
Human-readable assessment prose. Do not parse it.
Signal[]
required
Projected findings, including weak findings.
FamilyReport[]
required
Six projected family reports, one for each current evidence family.
Provenance | null
required
Assessment versions and exact edge build.
Network | null
required
Projected network context without the raw IP address.
Identity | null
required
Versioned identity output. Identity is separate from the verdict and never changes it.
string | null
required
Name of the edge recorded by ingest.
integer | null
required
Unix milliseconds assigned to the settled projection. The ingest route clamps out-of-range edge values to its arrival time.
integer | null
required
Unix milliseconds when the immutable projection was first ingested. Exact retries do not overwrite the settled row.

Verdict fields

Insufficient reasons

Signal object

string
required
Catalogue identifier. See Signal reference.
string
required
absolute, composite, conditional, or weak for this observation.
string
required
One of the six evidence-family IDs.
string
required
Human-readable finding title. Do not parse it.
string
required
Human-readable evidence and limits. Do not parse it.
The full assessment can add sensor_admission to a finding. The tenant projection removes that field before ingest.

Finding tiers

Tiers are categorical, not numeric. Distinct-family corroboration does not claim statistical independence.

Family report

string
required
network-geometry, transport-stack, transport-reachability, tls-construction, http-construction, or compute.
string
required
contradicted, consistent, or not-assessed.
string | null
required
Strongest non-weak finding in the family, or null when no finding above weak fired.
object
required
Tagged object with state. unavailable and not-yet-ruled also contain a prose reason.
Coverage shapes are:
A family has status contradicted when a non-weak finding fired, including a conditional finding. A measured family with no non-weak finding is consistent. Other coverage without a non-weak finding produces not-assessed. The full family report also contains a signals array. The tenant projection omits it.

Provenance

Network

Network classification is context and does not change the verdict. The projection omits raw IP, concealment indicators, and unchecked concealment checks.

Identity

instance is present only when canvas, fixed WebGL raster, or audio supplies an anchor. machine is present only when cores, display, and timezone are present. Platform participates in the machine digest when available. Missing IDs and components are omitted inside a non-null identity object. The IDs are deterministic digests over normalized components, identity version, scope, and a salt derived from the submitted public site key. Key rotation changes them. Compare IDs only within one version and key scope. They describe matching component material, not people. They do not establish global uniqueness, anonymity, irreversibility, collision freedom, or continuity through every software and hardware change.

Projection omissions

The tenant response does not include:
  • top-level assessment schema
  • contradicting_families
  • full concealment
  • full sensor
  • per-finding sensor_admission
  • geometry
  • family-level signals
  • full session record
  • raw IP
  • raw claims or the measured payload
  • detailed TCP, TLS, HTTP/2, or QUIC records

Field stability

Use IDs, enums, booleans, versions, provenance, and documented timestamps as structured inputs. Do not parse summary, headline, detail, network descriptions, collector failure reasons, or coverage reasons.