A single call
You send reference and probe in one POST and get the answer. No multi-step flow to maintain.
EgoFaceV
Identity verification
Prove it is the same person and that they are really there
Send the ID photo and a short video of the face, and it answers whether it is the same person and whether they are live, with the tolerance you define. It stores neither the photo nor the video: it processes in memory and discards.
Comparing two faces is the easy part. The hard part is knowing there is a person on the other side and not a photo of a person held up to the camera. That is why the video is not a whim: it is what rules out spoofing.
All in one system
The modules that run the operation
Passive liveness
The person does not have to turn their head or blink on cue. The analysis runs on the video they already recorded.
Video or photo
If the case does not allow video, it accepts a photo. You lose liveness, but the comparison still runs.
A tolerance you set
The threshold travels in the request or stays fixed per client. A bank and an attendance app do not need the same strictness.
A response with a score
Beyond yes or no, it returns the similarity score, so you can keep the trace or tune your own criteria.
One key per system
Each consumer gets its own key and its own default tolerance.
Why this one
What makes it different
It stores no biometrics
No photos, no videos, no face vectors. Everything is processed in memory and discarded on response; only the record that a query happened remains, with its score and date.
No face means no false match
If no face is detected in the reference or the probe, it returns an error rather than an ambiguous negative. That difference matters when someone disputes a result.
A decision, not a report
Your system acts on a boolean. Score and liveness stay available for the trace, not for you to interpret.
Built for several systems
Multi-tenant by design: the same service serves different products, each with its own key and threshold.
Who it's for
Where it is used
Remote customer onboarding
Field attendance control
Goods pickup and delivery
Online exams and assessments
Facility access
Remote document signing
The safest way to store a face is not to store it.
Biometric data is sensitive data in both Chile and Costa Rica. A service that never stores it cannot leak it, and takes your system out of the problem entirely.
Frequently asked
What people ask us most
No. They are processed in memory and discarded on response. Only the query record is kept: which system made it, what score it returned and when. Never images or face vectors.
Because a photo cannot tell a person from a photo of that person. Video allows the liveness check to run. If your case does not allow video, it still accepts a photo, but you lose that guarantee.
You do. The tolerance travels in each request or is configured as a default for your system.
Through the contact form. We define the use case, the volume and the tolerance, then hand over the key with the documentation.
What do you need to verify?
Tell us the use case and the volume. It is contracted through the form and we hand over the key with the documentation.