Platform Overview
NEUS is a verification and trust layer built around one loop:- Verify — User completes verification through hosted or SDK flow
- Receive — Get a portable proof receipt (
qHash) - Reuse — Apply the receipt for access, trust, monetization, and agent policy
Core Platform Surfaces
Hosted Verify
/verify is the canonical hosted path for login, checkout, and interactive verification.Proof Receipts
Portable trust artifacts that downstream systems can inspect and reuse.
Verifier Catalog
Verifier metadata, input expectations, and access tiers from the backend catalog.
Agent Integrations
Agents can hold identity proofs, delegation proofs, and MCP-mediated access to NEUS trust signals.
Design Principles
| Principle | Description |
|---|---|
| One hosted verify path | Not fragmented auth and checkout routes |
| One backend catalog | Not duplicated metadata maps across frontend, SDK, MCP, and docs |
| One proof lifecycle | Reused everywhere instead of re-verifying ad hoc |
| Private by default | Explicit public and discoverable modes when needed |
How It Works
Understand the Model
Read How Verification Works to understand requests, signer strings, verifiers, and hosted interaction.
Learn the Lifecycle
Read Verification Lifecycle for creation, async processing, terminal states, reuse, and revocation.
Core Concepts
How Verification Works
Requests, signer strings, verifiers, and hosted interaction.
Verification Lifecycle
Creation, async processing, terminal states, reuse, and revocation.
Receipts & Results
Proof receipt structure, field semantics, and downstream consumption.