mezein docs
mezein tells you an account belongs to a real, single person, without telling you who they are. These pages cover setting it up, your dashboard, reporting, and good practice.
Pick your platform
- Your site or app: a “Verify with mezein” button and three API calls. Get a key at app.mezein.com/platform in a minute.
- Discord: a bot that gives verified people a role.
- GitHub: an app that puts a verified-person check and label on pull requests.
How it works
- A pin
- Each person holds one: a passkey on their phone. They get it by being vouched for in person, at a table night, or with a university email (for now UCL, King's, Imperial, LSE, Oxford and Cambridge).
- A mezein ID
- When someone verifies with you, you get an ID for them: 26 characters, the same every time they verify with you, and different on every other platform. It's the only thing you learn. You can't use it to find them anywhere else, and nobody else can use theirs to find them on yours.
- Person
- Whether their pin is active now. It stops being true if mezein pauses or removes the pin, so check again from time to time.
- New
- True while their pin is under 30 days old or not yet confirmed by a second person. Treat new accounts a little more carefully on things that are easy to abuse.
- Reports
- When you find a fake or abusive account, tell us. One report opens a review; reports from two different platforms within 30 days pause the pin everywhere. See Reporting.
What mezein never shares
Names, emails, phone numbers, which university someone is at, or which other platforms they use. Your dashboard shows counts, and for sites, your own list of mezein IDs. That's all.