Most products use Sell access or Hosted sign-in: VerifyGate or Hosted Verify, then gateCheck on the server with the visitor’s account address. Use this page only when your backend creates proofs directly, or when you automate NEUS as your own profile.
When you need this
Backend proof creation (verifyFromApp)
After a user approves your product once (app-link permission), your server can create proofs for them without a per-request signature.
Requirements:
- Active user approval for your
appId and site origin (Agent permissions: App link)
X-Neus-App (from appId) and matching Origin on the request (appOrigin sets both for Node)
If approval is missing, send the user through Hosted Verify first.
This is not the same as creating a listing under Profile → Listings, which bills hosted checks to your account.
Profile access keys
Create keys under Profile → Account.
Pass the key to NeusClient as apiKey on the server. The SDK sends Authorization: Bearer npk_.... Never ship keys in browser bundles.
Access keys identify your builder profile for automation. They do not replace per-user approval for backend proof creation.
Billing
Published gates are the default billing source. Pass gateId on hosted checkout and gateCheck; NEUS resolves owner, usage, and payment from that gate.
appId is public attribution for advanced server flows. It does not bill your account by itself.
See Billing.
Next: API Authentication Last modified on August 20, 2026