VU cloud services

A real document doesn't guarantee its real owner

Face Analysis compares a person's selfie against the photo on their document and returns a similarity score from 0 to 100. One API call and you know whether it's the same person.

To generate your API Key, you need a paid VU plan.

Selfie of a personImage "0" · selfie
Identity document"1"
0
"biometric": {"0": {"1": 93}}93 ≥ 70 · same person

Security backed by certifications and independent testing

iBeta PAD Level 3 compliant

ISO/IEC 30107-3 · Liveness

ISO/IEC 27001:2022

Information security management

ISO/IEC 27017:2015

Security for cloud services

The problem

Having a valid document doesn't prove who is presenting it

A stolen, borrowed or irregularly acquired document passes document checks because it is authentic: the data matches and the format is correct. The question left unresolved is whether the face in the selfie belongs to its holder. When that comparison depends on a person reviewing two photographs, the process doesn't scale and leaves no auditable criterion.

Our solution

A score for every pair of faces. You set the threshold.

The service compares the faces sent and returns their level of similarity on a scale of 0 to 100. The decision isn't automatic: the internal policy you set evaluates the score at which identity is confirmed. Nor does the service verify whether the selfie belongs to a person who is present; that validation is done by Antispoofing Facial, which can be requested in the same call.

Case 01

You already have another provider

There's no need to migrate your whole operation to add biometric comparison. You can consume only this API, in parallel with your current provider.

Case 02

You need to verify returning customers

During registration, your customer's facial biometric vector is stored. In each new interaction, their selfie is compared against that vector, without having to ask for the document again.

Case 03

You're building your own product

You need the face comparison component, not a full platform. You integrate it into your solution and keep control over the rest of the process.

Key features

One call, the operations you choose

You declare, image by image, what you want to analyze. If you declare no operation, the biometric comparison runs by default.

01

1:1 biometric comparison

Measures the similarity between two faces with a score from 0 to 100. It's the default operation.

0threshold 70
0100
"biometric": {"0": {"1": 93}}
02

Antispoofing in the same call

The Antispoofing Facial result arrives nested in the same response, without a second request.

{
  "biometric": { … },
  "spoofing": { … }
}
03

Facial attributes

Signals to determine whether the capture is suitable.

  • sharpness
  • glasses
  • closed eyes
  • face mask
04

Head pose

Yaw and pitch, in degrees.

05

Iris position

Coordinates of both eyes.

Compare against the document or against a face you already stored

  • Selfie against document

    You send both images and get the similarity score between them. The document photo can come from ID Analysis, which delivers it already cropped.

  • Selfie against a stored vector

    You request the face's biometric vector, store it and use it in future comparisons, without needing to keep the photo. Also record the methodology you generated it with, since the score's scale varies by methodology.

  • Capture quality

    If you request attributes and pose in the same call, the response includes a quality verdict: high, medium or low. If the result is low, request a new capture before trusting the score.

  • Integration

    It does not replace Identity Link when you need a full verification. You can use it on its own or combine it with other VU cloud services.

The integration

Two endpoints and one decision rule.

No SDK and no dependencies. Call the API from your backend: The key is never exposed in a mobile app or the browser.

ElementHow it works
GET /versionChecks connectivity. The status code is evaluated, not the response body
POST /inferenceRuns the requested operations on the images you send
AuthenticationApi-Key header. Each service has its own key, per environment
Base URLVU provides it along with the key, depending on the environment
Inputinfo as a business reference, images in base64 and operations, one list per image
Outputid, code, message and biometric (similarity matrix from 0 to 100). The other fields depend on the operations you request
RequestPOST /inference
// Header: Api-Key: <your service key>
{
  "info": "onboarding-12345",
  "images": ["<selfie in base64>", "<face from the document>"],
  "operations": [["biometric"], ["biometric"]]
}
  • "biometric": {"0": {"1": 93}}93 is greater than or equal to 70. It's the same person: you confirm.
  • "biometric": {"0": {"1": 19}}Below the threshold. You don't confirm.
The decision ruleYour backend
if (status === 200 && body.biometric?.["0"]?.["1"] >= 70) {
    samePerson();
} else {
    notConfirmed();
}

Don't confirm by elimination

There is no error code that indicates "not the same person": when the faces don't match, the response arrives with code 200 and a low score. If your logic approves everything that isn't an explicit rejection, any unexpected response will end up turned into an approval.

The threshold of 70 applies to the default methodology. If you choose another, the score's scale changes and you'll need to calibrate your own threshold.

Image requirements

Capture quality decides how much the score is worth.

AspectValue
Recommended resolution360 × 360 or more*
FaceOnly one per image, facing forward and with eyes visible
FormatJPEG or PNG. If JPEG, quality 90 or higher
Encodingbase64 with no data: prefix and no line breaks

*The minimum accepted resolution is 160 × 160. Below that, the API returns an error.

Send 360 × 360 even though the minimum is lowerBelow 360 px the API answers just the same, with code 200, but the quality verdict drops to low. Aggressive compression also degrades the score. Capture quality is an integration decision: settle it at the start.
How you start

Self-service: connect this API with no middlemen

With a paid plan, you generate the key from VU's panel and call the service from your backend.

  1. 02

    You confirm accesswith the method the panel offers you

  2. 03

    You open Cloud Servicesin the side menu

  3. 04

    You choose Face Analysisamong the available services

  4. 05

    You generate the API keywith a paid plan, for the environment you're going to use

  5. 06

    You copy the key and call GET /versionto confirm connectivity

Generate your API Key

To generate your API Key, you need a paid VU plan.

Frequently asked questions

No. You can consume it independently, with its own key, over whichever flow you choose. It coexists with the provider you already have installed.
Yes. You can request the face's biometric vector, store it and use it in future comparisons, without having to keep the photo. Also record the methodology you generated it with, since the score scale varies by methodology.
70 is the reference threshold for the default methodology. Even so, the service doesn't make the decision for you: your policy defines the score from which you confirm the identity. If you use another methodology, the score scale changes and you'll need to calibrate your own threshold.
Not on its own. Biometric comparison measures how similar two faces are, but it doesn't verify whether the selfie belongs to a person who is present. That's what Antispoofing Facial is for, and you can request it in the same call; its result comes nested in the response, with no need for a second request.
In the Api-Key header of each request. Each service has its own key for each environment, and VU provides it along with the corresponding base URL.
If you request attributes and pose in the same call, the response includes a quality verdict: high, medium or low. If the result is low, request a new capture before trusting the score.

You already have the selfie and the document. The score is missing.

Generate your key and compare a pair you already know.

Generate your API Key

To generate your API Key, you need a paid VU plan.