Skip to main content
Follow this checklist when shipping a product that uses NEUS for verification, gating, or login. If you are experimenting solo with your own wallet, start with Quickstart and add platform setup when you publish an app.

​
1. Create your NEUS profile

  1. Open the NEUS platform and sign in (passkey or wallet).
  2. You will use Profile for app linking, Credits for balance, and Identity when you need domains or org proofs later.
This follows the Link app flow: domain, daily cap, and wallet signature.
  1. Go to https://neus.network/profile?tab=apps (Profile → Apps).
  2. Open Link app / Manage app.
  3. Enter your app domain (e.g. acme.com or https://app.acme.com).
  4. Set a daily credit cap (protects you from runaway usage).
  5. Complete the steps in the modal (wallet sign-in as needed).
When linking succeeds, you get an appId to send as X-Neus-App on API traffic from that integration. The SDK maps this automatically: 
import { NeusClient } from '@neus/sdk';

const client = new NeusClient({
  appId: 'your-app-id', // same value as X-Neus-App
});
appId is for attribution (which product called NEUS). It does not by itself move every bill to your org. To pay for users from your balance, add a sponsor grant (step 4).

​
3. Add credits (Credits tab)

  1. On the platform, open Credits and keep a balance on the wallet that should pay for your integration.
  2. If you only use user self-pay (each end user’s wallet pays), you still need credits on their side when they sign requests—see Billing.

​
4. Sponsor users

For products where end users should not manage NEUS credits:
  1. Keep your org wallet funded (step 3).
  2. Issue short-lived sponsor grants and pass them to the SDK as sponsorGrant (sends X-Sponsor-Grant).
const client = new NeusClient({
  appId: 'your-app-id',
  sponsorGrant: '<sponsor-grant-token>',
});
Grant issuance and caps: Partner setup (sponsor section) and Billing.

​
5. Choose an integration

OptionWhenNext step
Hosted VerifyYou want NEUS-hosted UI for login / verificationHosted Verify
WidgetsReact app, gates and badgesWidgets
SDKCustom browser or Node flowSDK overview → JavaScript
HTTP APIServer-onlyAPI overview
MCPCursor, Claude, agentsMCP overview
Not sure? Choose an integration path.

​
6. Production checklist

  • App linked on the platform with a realistic daily cap
  • Credits on the wallet that should pay (you or users, per your model)
  • appId on the client; sponsorGrant if you pay for metered calls
  • Billing understood (visibility vs who pays)
  • If you see 402, see x402 for pay-per-use retries

​
Without a linked app

Use Quickstart and Hosted Verify. Add Apps and sponsor grants on the platform when you publish an app that should pay for others.

Billing

Who pays, x402, sponsor model.

Partner setup

Domains, org verify, sponsor detail.

Integration

Verify → save → reuse loop.

Overview

Product summary.