Skip to main content
One proofId feeds gates, hub profile, and agents. Prefer the receipt ID over one-off signatures. Credits and sponsor grants are covered in Billing. For a local try first, use Quickstart, then complete the steps below before production traffic.

​
1. Create your account

  1. Sign in to the hub with passkey or wallet.
  2. Apps — register products your integration will call from. Credits — balance for the wallet that pays. Identity — domain or org proofs when your flow needs them.
  3. Use the wallet that should own billing and app registration for this product.
  4. Access keys — when you need a personal API key (same Authorization: Bearer token for api.neus.network and for MCP when you want account-scoped tools), open Access keys and generate one. You can skip this until you run scripts, server calls, or MCP flows that return auth_required.

​
2. Register your integration and capture appId

  1. Open Apps in the hub.
  2. Link app or Manage app.
  3. Enter your app domain (e.g. acme.com), set a daily credit cap, and finish the modal.
When registration succeeds, NEUS issues an appId for that integration. Send it as X-Neus-App on API traffic (the SDK maps this automatically). 
import { NeusClient } from '@neus/sdk';

const client = new NeusClient({
  appId: 'your-app-id', // same value sent as X-Neus-App
});
appId is an attribution identifier (which product made the request).
It does not by itself move charges to your organization wallet. Use sponsor grants when you want to pay on behalf of users.

​
3. Fund the wallet that will pay

  1. Credits tab → balance on the payer wallet.
  2. If users self-pay, they need credits on their wallet. See Billing.

​
4. Decide your billing model (sponsorGrant if you pay)

If your product should pay verification costs for end users, fund the org wallet, issue short-lived sponsor grants, and pass them to the SDK as sponsorGrant (maps to X-Sponsor-Grant). If users should self-pay, do not send sponsor grants. 
const client = new NeusClient({
  appId: 'your-app-id',
  sponsorGrant: '<sponsor-grant-token>',
});
Grant issuance and caps: Workspace setup and Billing.

​
5. Choose your integration path

DefaultNext
Hosted Verify (no embedded wallet)Hosted Verify
ReactWidgets
Custom JSSDK · JavaScript
AI toolsMCP
Advanced HTTPAPI
Ship loop: Integration · all options: Paths.

​
6. Production readiness checklist

  • Integration domain is registered with a realistic daily cap
  • Paying wallet has credits (yours or users’, based on your model)
  • Client sends appId and uses sponsorGrant only when sponsoring
  • Team understands Billing and x402 behavior
  • Verification receipts are stored and reused in your product logic

Billing

Who pays, x402, sponsor model.

Workspace setup

Domains, org verify, sponsor detail.

Integration

Verify → save → reuse loop.

Overview

Product summary.