Skip to main content

​
Default

Use hosted /verify or the SDK unless you must drive POST /api/v1/verification yourself.

​
Why sign

The signature shows the wallet agreed to that verification request. NEUS then issues the proof receipt.

​
HTTP outline

  1. POST /api/v1/verification/standardize — get signerString.
  2. Sign that string with the user’s wallet.
  3. POST /api/v1/verification — submit the same request fields as in step 1, plus signature.
Do not modify or invent the message text—sign only the string returned by standardize (or use standardizeVerificationRequest in the SDK).

​
Message shape

NEUS Verification Request
Wallet: <address>
Chain: <chainId or CAIP-2 chain>
Verifiers: <comma-separated-ids>
Data: <json payload>
Timestamp: <unix-ms>

​
SDK

import { standardizeVerificationRequest, signMessage } from '@neus/sdk';
// See JavaScript SDK docs for a full example.

​
Wallets

TypeStandard
EOAEIP-191
Smart contractEIP-1271
CounterfactualEIP-6492

How verification works

Flow overview.

API authentication

HTTP signing entry.

Verifier catalog

Verifier IDs.

CAIP-380

Portable proof envelope.