Skip to main content
Get started covers first-touch onboarding. This page is payer mechanics, sponsor detail, x402, and edge cases.

​
Attribution and charges

appId on NeusClient sends X-Neus-App so NEUS can attribute usage to your product. It does not, by itself, move the bill to your NEUS account balance. Billed wallet comes from authentication: signing wallet, sponsor grant, x402 receipt, or some gate setups. Until one applies, appId alone does not move billing. End users may still need credits or another payer.

​
Apps vs individuals

You are…PriorityBilling
Building an appUsers should not hit random “out of credits” walls; you want predictable costYou pay for metered verification and checks via sponsor grants (and credits on your org wallet in the platform). Users only see hosted verify / your UI.
Using NEUS for yourselfYour own proofs and profileYou pay with your NEUS credits (or x402 when you run out). appId is optional (attribution only).
Same SDK and API. Different who funds credits.
  1. Platform: app + credits on the org wallet for that app.
  2. Sponsor users: short-lived X-Sponsor-Grant so calls debit your org balance, not the end user’s.
  3. SDK: new NeusClient({ appId: '…', sponsorGrant: token }) labels and pays under the grant.
Details and grant flow: Platform setup.
Anonymous heavy gate checks / verification without a payer context ≠ production sponsored limits. No sponsor, no signature, no receipt: dev or very low volume only.
  1. Use hosted verify or SDK with your own wallet.
  2. Credits come from your NEUS balance on that wallet.
  3. 402: x402 + PAYMENT-SIGNATURE retry. x402

​
How NEUS selects the payer

Precedence: paid receipt → sponsor grant → gate owner pays (if set) → signing wallet → x402 → else limits / payment required. Payer comes from crypto/session mechanics, not a “bill this appId” body field.

​
SDK configuration

ConfigEffect
appIdX-Neus-App · attribution
sponsorGrantX-Sponsor-Grant · org pays when valid
paymentSignaturePAYMENT-SIGNATURE · after 402
The SDK does not auto-complete x402 payments; your app handles 402 → pay → retry (or you avoid 402 by keeping org credits healthy).

​
Visibility vs billing

  • Public / unlisted: eligibility without sign-in.
  • Private: visibility rules apply; billing is separate.

x402

Pay-per-use when credits run out.

Platform setup

Apps, domains, sponsor grants.

Security & trust

Privacy defaults.

SDK overview

Client setup.

​
When the app owner pays

“App owner pays everything” uses sponsor grants and org credits, not appId alone.