NEUS Docs

One weak check is easy to game. Publish a listing that layers hosted account signals so visitors must pass more than one requirement.

Layer	Check ID	When
Social / work account	`ownership-social` or `ownership-org-oauth`	Linked identity most products need first
Human	`proof-of-human`	Anti-bot and fair access
Account uniqueness	`ownership-basic`	Baseline uniqueness when you also need a signed account check

Prefer social + human for consumer apps. Add ownership-basic or wallet-risk only when your threat model needs them.

Publish the layered gate

In Profile → Listings, require the checks above, set pricing, and publish. Visitors never see your API key — they only need your gateId.

VerifyGate

<VerifyGate
  gateId="gate_layered"
  onVerified={(result) => {
    // persist result.qHash for replay protection
  }}
>
  <button>Verify to continue</button>
</VerifyGate>

Server eligibility

const layered = await client.gateCheck({
  gateId: 'gate_layered',
  address: user.accountAddress, // from Hosted Verify / proof subject
});

Configure recency on the gate for point-in-time checks. Store proof IDs (qHash) where replay matters.

Next: Create a listing · Hosted Verify · Pricing

Last modified on August 10, 2026

Playbooks

Abuse and layered access

Publish the layered gate

VerifyGate

Server eligibility

​Publish the layered gate

​VerifyGate

​Server eligibility

Publish the layered gate

VerifyGate

Server eligibility