qHash as the SDK. For product checkout, publish a gate and pass its gateId; NEUS resolves the gate policy, billing owner, credits, sponsor/x402 behavior, and attribution server-side.
Base URL: https://api.neus.network
Browsers
Send end users through the JavaScript SDK or Hosted Verify. If a web client needs behavior outside those surfaces, your backend should call NEUS so secrets stay off the client and CORS stays predictable.Reads vs writes
| Operation | Typical use |
|---|---|
| GET (below) | Eligibility and proof reads |
POST /api/v1/verification | Create a proof (Authentication); prefer the SDK or Hosted Verify unless you need raw HTTP |
Endpoints
| Path | Method | Purpose |
|---|---|---|
/api/v1/proofs/check | GET | Eligibility (gates) |
/api/v1/proofs/by-wallet/{address} | GET | List by wallet |
/api/v1/proofs/{qHash} | GET | Fetch by qHash |
/api/v1/verification | POST | Create proof (server) |
/api/v1/verification/standardize | POST | Phase 1 of raw HTTP: returns signerString for the exact body you will submit |
/api/v1/verification/verifiers | GET | Verifier catalog |
Examples
By walletproofs, totalCount, hasMore, and continuation fields:
nextCursor— preferred for owner vaults and large histories (keyset paging).nextOffset— used when the merged vault is multi-wallet or cursor is unavailable.
cursor (not offset) on the next request when nextCursor is present:
verifierIds checks are for advanced protocol tooling. Product access checks should use gateId.
Create a proof (raw HTTP, advanced)
Most products use the SDK or https://neus.network/verify. Raw HTTP is a fixed two-phase flow:
- Build the final JSON body.
POST /api/v1/verification/standardizewith that body.- Sign the returned
signerString. POST /api/v1/verificationwith the same body plussignature.
signerString before retrying step 4.
Catalog
Auth
- Reads: public and unlisted proofs are often open; private proofs require permitted access.
- Writes: follow Authentication (signature, session, or app-attributed rules).
Next
Get started
Account, app, billing.
Authentication
Keys, delegation, signing.
Errors
HTTP error codes.