Developers
Stop bots and duplicate accounts. UNC Pass tells your app that a user is a unique, identity-verified human — and nothing else about them.
Your app never receives the person's name, email, phone, documents, photos or balance. The person sees exactly what you will learn and can remove your app from UNC Pass at any time.
1. Get an API key. Join the UNC developer programme in the app, create an app and enable the unc_pass scope.
2. Start a request from your server and show the person the code, or a QR code of the qr value:
curl -X POST https://api.unctech.co/api/v1/pass/requests \
-H "X-API-Key: unc_dev_..." -H "Content-Type: application/json" \
-d '{"age_over_18": true, "country": false}'
{"request_id": "9f2c...", "code": "K7QM-4XTD",
"qr": "uncapp://pass?code=K7QM-4XTD", "expires_at": "..."}3. The person approves in the UNC app (Account & Security → UNC Pass), by scanning the QR or typing the code. Requests expire after 10 minutes.
4. Fetch the result from your server (poll every few seconds):
curl https://api.unctech.co/api/v1/pass/requests/9f2c... \
-H "X-API-Key: unc_dev_..."
{"request_id": "9f2c...", "status": "approved",
"human": true, "uid": "3b1f0c...", "age_over_18": true}status is pending, approved, denied or expired. Store uid to recognise the same person next time — one uid, one account.
Keep your API key on your server. Never put it in a website or mobile app.
UNC Pass is in early access for approved developers. Usage is counted per verification; pricing will be announced before any charge applies.
Verification reflects UNC's identity checks at the time of the request. It confirms a unique, verified account — it is not a background check or a guarantee about the person.