NEUS runs sign-in and verification in the browser. Your app saves the receipt and checks it before payouts, access, or other trusted actions.
End users never need a NEUS account, an API key, or extra setup in your product.
1. Create and publish a gate
- Sign in at neus.network.
- Open Gates in your profile and choose the checks visitors must pass.
- Set pricing (you pay by default, or charge visitors).
- Publish and copy your checkout link or embed snippet.
Your gate stores the check policy. Visitors only need your gateId.
2. Protect your UI with VerifyGate
import { VerifyGate } from "@neus/sdk/widgets";
<VerifyGate gateId="gate_your-app-name">
<ProtectedContent />
</VerifyGate>;
VerifyGate looks for an existing receipt, opens Hosted Verify when a new one is needed, then shows your content. Wallet, passkey, and OAuth all happen on NEUS — not inside your app.
3. Or send users to Hosted Verify
import { getHostedCheckoutUrl } from "@neus/sdk";
window.location.assign(
getHostedCheckoutUrl({
gateId: "gate_your-app-name",
returnUrl: "https://myapp.com/auth/callback",
}),
);
qHash from the callback URL or popup message. Details: Hosted Verify.
4. Check before trusted actions
On your server, confirm the visitor still satisfies the published gate before you act:
import { NeusClient } from "@neus/sdk";
const client = new NeusClient();
const result = await client.gateCheck({
gateId: "gate_your-app-name",
address: user.walletAddress,
});
if (!result.data?.eligible) {
// send the user back to VerifyGate or hosted verify
}
Assistants and agents
Connect MCP hosts:
npx -y -p @neus/sdk neus setup
npx -y -p @neus/sdk neus auth
npx -y -p @neus/sdk neus doctor --live
neus auth for OAuth in your browser. Access keys are for servers, CI, and automation — never in browser code. Call neus_context first in each MCP session.
Agent wallets: Agent verification flow.
Advanced server receipts
Need backend-created receipts after a one-time user approval? See Integrations.
Next: Integration Last modified on June 5, 2026
