NEUS Docs

NEUS bills metered verification usage to a NEUS profile. Credits spend first. Hosted sign-in for your app does not use credits. Credits apply when a trust check runs, a receipt is saved, or Pro hosted AI is used. Plan amounts and the live credit estimator: Pricing · neus.network/pricing.

How money moves on NEUS

Three lanes cover every flow. Most products only use the first.

Lane	Who pays	Use it for
You pay for checks	Your NEUS credits	The default — verifications through your gate bill your account
Charge visitors at a gate	Your visitor	Paid content and member access — card or USDC at checkout
Charge per API call (metered)	The caller / agent	Metered APIs and agents that pay as they go (`x402`)

Default: you pay for visitor checks

When you publish a gate, you own it — so verifications through that gate bill your NEUS account by default. Visitors embed or link your checkout with one public gateId:

<VerifyGate gateId="gate_your-app-name" />

There is no app ID or billing wallet to copy for this path. The gate carries the check policy and the payer.

Server checks

Confirm eligibility before trusted actions with gateCheck — pass the same gateId and the visitor’s account address (from Hosted Verify / the receipt subject):

const result = await client.gateCheck({
  gateId: 'gate_your-app-name',
  address: user.accountAddress,
});

if (result.data?.gate?.allRequiredSatisfied !== true) {
  // Send the visitor back to Hosted Verify
}

Charge visitors instead

A gate can charge visitors directly. Turn it on in the gate’s pricing step. Your NEUS credits still cover the verification checks unless you configure otherwise. Card: connect a payout account once from Treasury → Payouts. Card payments for your paid gates then settle to that account. USDC checkout (optional): for products that already support stablecoin payers. Not required for account-based products. Until payouts are connected, paid gates may offer USDC checkout only. Payment runs after verification by default. For the full checkout sequence, see Hosted Gate Checkout.

When your app creates agents for users

Agent setup creates two separately signed receipts. Billing follows the signer for each step unless a validated sponsor or pay-per-call receipt is present.

Step	Default payer
Agent signs `agent-identity`	Agent account
Signed-in account signs `agent-delegation`	Signed-in approving account
Server signs with its own profile	Builder profile account
Valid sponsor grant	Sponsoring organization
Valid pay-per-call receipt	Caller that bought the receipt

For a dedicated agent account, create identity first, then send the user through the delegation-only hosted callback. See neus_agent_create.

When credits run out

Billable calls return 402 with a quote. Complete payment and retry with PAYMENT-SIGNATURE.

Advanced server integration

Server-side receipt creation and per-user approvals use separate flows — see Integrations. Next: Pricing · x402

Verification

Platform

SDK

Widget UI

API

Billing

How money moves on NEUS

Default: you pay for visitor checks

Server checks

Charge visitors instead

When your app creates agents for users

When credits run out

Advanced server integration

​How money moves on NEUS

​Default: you pay for visitor checks

​Server checks

​Charge visitors instead

​When your app creates agents for users

​When credits run out

​Advanced server integration

How money moves on NEUS

Default: you pay for visitor checks

Server checks

Charge visitors instead

When your app creates agents for users

When credits run out

Advanced server integration