Skip to main content

​
Cookbook Overview

Real-world integration patterns for NEUS verification.

​
By Use Case

Auth + Hosted Verify

Standardized /verify login and hosted popup flow for authentication.

NFT Gating

Gate content behind NFT ownership verification.

Domain Verification

Verify domain ownership with DNS TXT records.

Sybil Resistance

Prevent Sybil attacks with proof-based identity verification.

Verifiable Agents

Create and delegate agent identities for AI systems.

Hub Integrator Setup

Org/domain setup, app linking, sponsor grants, and partner rollout.

MCP Server

Hosted MCP for agents, tool calling, and human-in-the-loop verify flows.
StepGuideWhen to Read
1Auth + Hosted VerifyYour product needs the canonical hosted path
2NFT Gating or Domain VerificationConcrete end-user policy examples
3Sybil Resistance and Verifiable AgentsTrust requirements become stricter
4Hub Integrator SetupOperationalizing app attribution, sponsorship, and partner rollout

​
Integration Patterns

1

Choose Your Flow

Pick the right pattern for your use case: hosted verify, custom SDK, or widget integration.
2

Configure Verifiers

Set up the required verifiers and their input data for your specific policy.
3

Handle Verification

Implement the verification flow with proper error handling and retry logic.
4

Enforce Gates

Use proof receipts to gate access and enforce trust boundaries.