Open APIs · three rails
Prove the fund. Prove the signer. Then bind the paper.
A tick-box NDA is not evidence. Singapore needs a named person, an active LEI, and a signature method that identifies them. We do not build that. We plug it.
The stack
Entity identity is free and open. Person and fund KYB is a compliance platform. The signature is a separate envelope with its own evidence file.
Entity
GLEIF
Always on · api.gleif.org — open, no key
Legal Entity Identifier. Active vs lapsed. Legal name. Parent. Free. This is the fund, not the person.
Person + fund
Sumsub
Primary KYC/KYB · REST + webhooks + hosted Unilink
Passport + liveness of the signatory. Registry + UBO of the fund. AML/PEP. 220 countries. One Cockpit for counsel.
Person + fund
Persona
Alternative · REST + Inquiry SDK
Same job as Sumsub, more configurable flows per seat type (GP vs counsel vs family office).
Then bind
Bind
Docusign + IDV
Primary sign · eSign REST API 2.1 + IdentityVerifications
Envelope of the house NDA. ID check at the moment of signature. Audit trail. ETA-recognised in Singapore. IDV uses Onfido/IDnow in EMEA, IDVerse in ANZ.
Bind
Dropbox Sign
Faster DX · REST + embedded request
Cleanest developer API. Embedded iframe in the room. SMS check. Weaker identity-at-sign than Docusign IDV. Good for the preview; not the live close.
Bind + ID
OneSpan Sign
One contract · Identity Verification REST API
Bank heritage. ID, biometrics, and signature in one transaction. Heavier sales cycle. Use if counsel wants a single evidence file.
What we would ship
- 01 GLEIF lookup on the LEI field. If the record is lapsed or the legal name does not match the fund, the NDA does not file.
- 02 Sumsub Unilink for the signatory — passport, liveness, director/partner capacity — and KYB of the vehicle. Webhook writes a verification id onto the seat. No images stored here.
- 03 Docusign envelope of house NDA v2, IDV required. Completed PDF + certificate of completion land in the vault folder the GP can see. Our file records envelope id, template hash, and time.