Skip to main content
GET
Tenant verdict endpoint
Call the tenant verdict endpoint from your backend:
The secret key scopes the read to one site. Keep it out of browser code.

Request ID

Use the raw 32-character lowercase hexadecimal request ID returned by ordinary collection. The endpoint tolerates one legacy req_ prefix for compatibility, but new integrations must pass the raw ID unchanged.

Server example

A curl request uses the raw nonce:

Status codes

The endpoint returns plain text for 401 and 404. Cross-site and missing IDs deliberately share 404. The route defines no application-level 429 contract. Treat other statuses as unexpected HTTP failures, not assessment verdicts.

Availability

Successful ordinary collection means D1 acknowledged a tenant-visible commit. The authenticated owning tenant can retrieve the returned ID immediately. Projection failure makes collection fail instead of returning a request ID. The 60-second settlement threshold and 30-second sweep apply only to local NDJSON persistence. ZDR creates no tenant row.

Success response

A 200 response returns tenant API version 1:
The prose and sample values are illustrative. The six family reports are part of the current assessment projection. network, identity, provenance, edge, and timestamps can be null when the stored row lacks valid values. Inside a non-null identity object, missing IDs and components are omitted. See Tenant verdict schema for every field.

Projection boundary

The endpoint does not return the full edge assessment or session. It omits:
  • the full session and raw measured or declared claims
  • raw IP and detailed transport records
  • geometry arithmetic
  • the full concealment report, apart from projected network classification
  • the sensor report and per-finding sensor admissions
  • contradicting_families
  • each family report’s internal signal-ID list
A tenant secret key authorizes this projection. It is not an edge operator credential.

Stable fields

Use documented IDs, enums, booleans, versions, provenance, and timestamps as program inputs. Treat summary, signal headline, signal detail, network descriptions, and coverage reasons as prose. The endpoint reports an assessment. It does not prescribe a consequence.