NEUS Docs | Portable Trust Infrastructure

This is the selling-access recipe. Connecting an assistant? Add the hosted MCP endpoint. Adding sign-in to an app? Use hosted sign-in.

Publish once. One listing owns the checks, price, and hosted sign-in. Your app adds the gate and confirms the result; it never recreates the check logic. Visitors never need an API key.

Build it

Publish a listing

Add VerifyGate

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

<VerifyGate gateId="gate_your-app-name">
  <ProtectedContent />
</VerifyGate>;

VerifyGate reuses a saved proof or opens hosted sign-in on NEUS when a new one is needed. Wallet, passkey, and OAuth all happen on NEUS, not inside your app.

Confirm on your server

Pass the visitor’s account address (from NEUS sign-in or the saved result; passkey and OAuth included, no separate wallet required):

import { NeusClient } from '@neus/sdk';

const client = new NeusClient();
const result = await client.gateCheck({
  gateId: 'gate_your-app-name',
  address: user.accountAddress, // from hosted sign-in / stored proof subject
});

if (!result.data?.gate?.allRequiredSatisfied) {
  // send the user back to VerifyGate or NEUS sign-in
}

The visitor’s proof is theirs. If they return or visit another gate that needs the same checks, they can reuse it. You choose who pays. Use your NEUS credits for free access, or turn on visitor checkout and set a price. See Billing for card, USDC, and metered API options.

Optional: show proof status

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

<ProofBadge qHash={proof.qHash} />;

Pass showChains only when on-chain status matters in your interface.

import { getHostedCheckoutUrl } from '@neus/sdk';

window.location.assign(
  getHostedCheckoutUrl({
    gateId: 'gate_your-app-name',
    returnUrl: 'https://myapp.com/auth/callback',
  }),
);

Read the proof ID (qHash) from the callback URL or popup message, then store it. Details: Hosted sign-in.

Connecting an assistant instead?

Connect NEUS, then ask: “Before I take a sensitive action, use NEUS. Reuse what I already have.”

VerifyGate

Props, modes, and OAuth.

Hosted sign-in

The browser flow on NEUS.

Start

One command for assistants. Hosted sign-in for apps.

Backend-created proofs after a one-time approval: Integrations.

Start

Sell access with one gate

Build it

Optional: show proof status

Connecting an assistant instead?

Next

VerifyGate

Hosted sign-in

Start

​Build it

​Optional: show proof status

​Not using React? Send users to NEUS for sign-in

​Connecting an assistant instead?

​Next

VerifyGate

Hosted sign-in

Start

Build it

Optional: show proof status

Not using React? Send users to NEUS for sign-in

Connecting an assistant instead?

Next