VerifiedOS serves two distinct audiences with the same receipt:
The agent consumer
AI agents and developers need:
- Stable schemas — Predictable request and response structures that can be integrated into automated workflows.
- Machine-readable outcomes — Typed result states (VERIFIED, CHALLENGED, UNVERIFIED) that drive conditional logic.
- API-key attribution — Tenant-scoped execution with clear identity and billing boundaries.
- Canonical JSON — A portable, hashable receipt format that can be stored, forwarded, and independently validated.
The human consumer
Business operators and decision-makers need:
- Context — What was claimed, what evidence was supplied, and what was the verification scope.
- Provenance — Which models assessed the claim, where they agreed, and where they disagreed.
- Control — The ability to inspect, challenge, and preserve the verification record.
- Accountability — A receipt that can be presented to clients, regulators, or management as evidence of due diligence.
One receipt, two views
The VerifiedOS receipt is a single canonical JSON object that supports both a human-readable view and a machine-readable view. The human view surfaces the narrative — the claim, evidence, assessments, dissent, and adjudication in natural language. The machine view exposes the structured data — typed fields, hashes, signatures, and identifiers.
Both views are derived from the same immutable record. Neither can exist without the other.