NEUS Docs

Default: Hosted Verify or SDK client.verify() - you do not need to read this page to ship. Use this reference when you implement raw POST /api/v1/verification or debug SIGNATURE_VERIFICATION_FAILED / invalid signature responses.

Why

The wallet agrees to the exact request; NEUS returns a qHash and the complete portableProof envelope to the creator. The signature authenticates the request, not the later verifier outcome.

Raw HTTP only

If you call the API without the SDK:

Build the verification JSON body you will submit.
POST /api/v1/verification/standardize with that body to signerString (exact bytes to sign).
Sign signerString.
POST /api/v1/verification with the same body + signature.

Do not hand-edit the six-line text. Only sign what standardize returns (or SDK standardizeVerificationRequest) for that exact body.

Troubleshooting

Re-run /standardize on the same payload and compare signerString to what the wallet signed.
walletAddress, verifierIds, data, signedTimestamp, and chain fields must match between standardize and submit.
Do not remove nonces or timestamps from data when recomputing qHash; every data field is bound.

Shape

UTF-8, LF newlines.

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

SDK helpers

import {
  standardizeVerificationRequest,
  signMessage,
  verifyPortableProofEnvelope,
} from '@neus/sdk';

Wallets

Type	Standard
EOA	EIP-191
Contract	EIP-1271
Counterfactual	EIP-6492

How it works

Flow.

API auth

HTTP.

Verifiers

Ids.

CAIP-380

Envelope.

Overview

Checks

Platform

SDK

Widgets

API

Signing format

Why

Raw HTTP only

Troubleshooting

Shape

SDK helpers

Wallets

How it works

API auth

Verifiers

CAIP-380

​Why

​Raw HTTP only

​Troubleshooting

​Shape

​SDK helpers

​Wallets

​Related

How it works

API auth

Verifiers

CAIP-380

Why

Raw HTTP only

Troubleshooting

Shape

SDK helpers

Wallets

Related