XityConnect
How verification works
A relying party asks a question The system answers yes or no, with a signed proof The underlying evidence is never returned
The flow
Five steps, all logged
01
Request
A relying party requests a specific claim about a subject
02
Consent
The subject consents to the disclosure of that claim
03
Evaluate
The system checks current identity state on-chain
04
Answer
A signed yes/no with proof is returned to the relying party
For relying parties Relying parties receive yes/no answers with signed proofs They never see identity evidence The public role returns only balance, nonce, and existence, never public keys, identity names, or address-to-identity linkages
For developers
Verify a claim in seconds
The verification endpoint is part of the public API See the developer portal for the full reference
GET/claims/{subject_id}/verify?claim=over_18Verify an age claim without DOB
GET/credentials/{credential_id}Check a credential is valid
POST/auth/challengeBegin a challenge-response session