Mobai Document Manager

Freeze a document, bind a face to it, sign it, and let a stranger check it

This service does one thing: it takes a document, has Mobai bind a live face to the exact bytes of it, embeds Mobai's signed statement inside the file, and then gets the whole thing signed twice. What comes out is a PDF that anyone can verify without asking us anything.

Employer

Drafts and sends from the CLI; this page shows status — state, versions, audit trail, and the command that moves a case on.

Open

Applicant

Arrives by link. Read the terms, consent, look at the camera, sign.

by invitation

Verifier

Upload a document. Paper checks first; the camera only if they pass.

Open

API and CLI

Everything above is a client of the same routes. So is an agent.

OpenAPI

What this proves, and what it does not

It proves
that a live person was present when this document was bound, that the document has not changed by a byte since, that both parties signed the same bytes, and that the person in front of a camera later is or is not that same person. All of it checkable from the file.
It does not prove
who that person is. Phases 1 to 3 bind a face and a liveness check with typed identity claims: enrolment, not identity proofing. Real passport-chip proofing is Phase 4, and the document says which one it is in the stamp rather than leaving it to be assumed.
It is not qualified
The signatures are made by a stand-in, not by a QTSP. Buypass attaches later through the same interface, signing exactly the bytes the stand-in signs, so the file format does not change when they do.