Skip to main content
Base: https://api.neus.network Billing. Get started, Billing. Create proofs. Hosted Verify at https://neus.network/verify, Quickstart, or widgets. Use HTTP for checks and reads. Use POST /api/v1/verification only when you need raw HTTP (Authentication).

​
Endpoints

PathMethodPurpose
/api/v1/proofs/checkGETEligibility (server gates)
/api/v1/proofs/by-wallet/{address}GETList by wallet
/api/v1/proofs/{qHash}GETFetch by id (qHash same as SDK proofId)
/api/v1/verificationPOSTCreate proof (advanced - see Authentication)
/api/v1/verification/standardizePOSTMandatory phase 1 for raw HTTP: exact signerString for the body you will submit
/api/v1/verification/verifiersGETCatalog

​
Examples

By wallet 
curl "https://api.neus.network/api/v1/proofs/by-wallet/0x...?limit=50"
Public / unlisted: anonymous ok. Private: requires access as the proof owner (Authentication). Check 
curl "https://api.neus.network/api/v1/proofs/check?address=0x...&verifierIds=ownership-basic"
Create a proof For most apps, create proofs via the SDK or the hosted browser flow at https://neus.network/verify (Hosted Verify). Raw HTTP is a strict two-phase handshake, not a single-step request:
  1. Build the exact JSON body you will submit.
  2. POST /api/v1/verification/standardize with that body.
  3. Sign the returned signerString.
  4. POST /api/v1/verification with the same JSON body plus signature.
If phase 2 fails with a signature error, re-run phase 1 on the same payload and compare the signer string. Shapes: API reference on the documentation site. Catalog 
curl https://api.neus.network/api/v1/verification/verifiers

​
Auth

  • Reads: public and unlisted proofs without a caller; private proofs only with allowed access.
  • Writes: wallet signature, or authenticated caller when the API accepts it—Authentication

​
Next

Get started

Onboarding.

Authentication

Signing.

Errors

Codes.