Skip to main content
Pick your surface — app, agent, or backend. NEUS gives you the same portable trust receipts everywhere.
You are buildingSimplest pathStart
Sign-in or access for your appHosted Verify — sign-in or gate checkout on NEUSTrust stack · Hosted Verify
Gated content or checkout<VerifyGate> + one published gateIdQuickstart
An agent or AI workflowOne-command MCP setupInstall NEUS
A backend in any languageHTTP API and server checksAPI overview

​
Apps: drop-in widgets

VerifyGate and ProofBadge are the lowest-friction way to ship trust. Your app never implements verifier logic — the gate owns the checks, pricing, and checkout.
1

Publish a gate

Sign in at neus.network, open your profile → Portals, choose the checks visitors must pass, set pricing (you pay by default, or charge visitors), and Publish. Copy your gateId.
2

Gate your content

import { VerifyGate } from '@neus/sdk/widgets';

<VerifyGate gateId="gate_your-app-name">
  <ProtectedContent />
</VerifyGate>;
VerifyGate reuses an existing receipt, opens Hosted Verify only when one is needed, then renders your content.
3

Show verified status

import { ProofBadge } from '@neus/sdk/widgets';

<ProofBadge qHash={proof.qHash} showChains />;
The receipt ID in API responses is qHash — save it if your server needs to look up the receipt later.
End users never need a NEUS account or API key. To confirm eligibility on your server before trusted actions and to use a hosted link instead of React, follow the full Quickstart.

​
Agents and assistants: one command

neus setup
neus check
Wires hosted NEUS MCP into Cursor, Codex, VS Code, and Claude Code. Then ask your assistant: “Use NEUS Verify before taking sensitive actions.” Codex only: neus setup --client codex, then neus auth --client codex. Details: Install NEUS · Agent verification flow

​
Backends: API and access keys

Use the HTTP API from servers, workers, and CI — never from end-user browsers. Eligibility, reads, and verification all return the same trust receipt ID (qHash). Server automation uses a profile access key from Profile → Keys (npk_*). Details: API overview · Integrations Next: Quickstart · Integration
Last modified on June 20, 2026