NEUS Docs

NEUS is one hosted trust layer. Sign-in, checks, gates, and agents share the same browser surface, the same receipts, and the same profile — you do not stitch separate auth and verification products.

The loop

Step	What happens
1	Check whether a valid trust receipt already exists
2	Verify only when the receipt is missing, stale, or needs a stronger decision
3	Save the receipt on a person, org, or agent profile
4	Reuse before access, payment, delegation, or action

Same loop in your app (VerifyGate), on your server (gateCheck), in MCP, and on NEUS itself.

Four pieces builders should know

Piece	Plain language	Where it lives
Profile	Your portable home on NEUS — identity, receipts, agents, and what you choose to show publicly	neus.network/profile
Hosted Verify	Browser sign-in and trust checks NEUS runs for you — passkey, wallet, OAuth, human, social	`neus.network/verify`
Check	One atomic trust decision (identity, ownership, human, wallet safety, agent permission, …)	Verifier catalog
Portal / gate	A published bundle of checks (and optional visitor pricing) you embed with one `gateId`	Profile → Portals · Create a portal

Sign-in (intent=login) creates a NEUS session for Hub and profile work. Gate checkout (gateId) creates or reuses trust receipts for your product. Both run on Hosted Verify — no wallet or passkey code in your app.

Who needs what

You are building	Start here	Credits apply to
Sign-in for your app	Hosted login with `intent=login`	Trust checks and saved receipts — not session sign-in
Access before content or payout	Quickstart — publish a portal, embed `VerifyGate`	Checks through your gate
AI assistant in the IDE	Install NEUS — OAuth + MCP	Checks when the assistant verifies or saves receipts
Server automation	Profile → Keys + Integrations	API checks and receipt creation

Profiles, agents, and access

People and orgs sign in once, collect receipts on their profile, and reuse them at gates.
Agents register identity, receive scoped permission from a controller account, and carry the same receipts into production gates and MCP.
Builders publish portals from their profile; visitors only need your public gateId — not a NEUS account, unless your gate requires it.

Denials leave receipts too, so partners and auditors see a complete record.

Integration loop

Check, verify, save, reuse.

Hosted Verify

Sign-in and checkout in the browser.

Pricing

Credits for checks — plans unchanged.

Agent concepts

Identity, permission, and delegation.

Verification

Platform

SDK

Widget UI

API

Trust stack

The loop

Four pieces builders should know

Who needs what

Profiles, agents, and access

Next

Integration loop

Hosted Verify

Pricing

Agent concepts

​The loop

​Four pieces builders should know

​Who needs what

​Profiles, agents, and access

​Next

Integration loop

Hosted Verify

Pricing

Agent concepts

The loop

Four pieces builders should know

Who needs what

Profiles, agents, and access

Next