Skip to main content
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

StepWhat happens
1Check whether a valid trust receipt already exists
2Verify only when the receipt is missing, stale, or needs a stronger decision
3Save the receipt on a person, org, or agent profile
4Reuse 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

PiecePlain languageWhere it lives
ProfileYour portable home on NEUS — identity, receipts, agents, and what you choose to show publiclyneus.network/profile
Hosted VerifyBrowser sign-in and trust checks NEUS runs for you — passkey, wallet, OAuth, human, socialneus.network/verify
CheckOne atomic trust decision (identity, ownership, human, wallet safety, agent permission, …)Verifier catalog
Portal / gateA published bundle of checks (and optional visitor pricing) you embed with one gateIdProfile → 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 buildingStart hereCredits apply to
Sign-in for your appHosted login with intent=loginTrust checks and saved receipts — not session sign-in
Access before content or payoutQuickstart — publish a portal, embed VerifyGateChecks through your gate
AI assistant in the IDEInstall NEUS — OAuth + MCPChecks when the assistant verifies or saves receipts
Server automationProfile → Keys + IntegrationsAPI 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.

Next

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.
Last modified on June 20, 2026