# Capabilities

### Liveness <a href="#prova-de-vida" id="prova-de-vida"></a>

**Objective**: verify whether the user is real and alive at the moment of the selfie capture.

**Possible responses**:

* `YES` — user alive.
* `NO` — failed liveness attempt.

{% hint style="info" %}
To use Liveness  in by Client, the Unico SDK implementation is mandatory.
{% endhint %}

### Identity Verification <a href="#verificacao-de-identidade" id="verificacao-de-identidade"></a>

**Objective**: ensure that the face being submitted belongs to the holder of the identification document number.

**Possible responses**:

* `YES` — face corresponds to the holder of the identification document number.
* `NO` — does not correspond to the holder of the identification document number.
* `INCONCLUSIVE` — insufficient evidence to determine whether the face corresponds to the holder of the identification document number.

{% hint style="info" %}
If the response is "inconclusive", we can orchestrate with the Risk Score and return a probabilistic response.
{% endhint %}

### Behavior Alert <a href="#alerta-de-comportamento" id="alerta-de-comportamento"></a>

**Objective**: complement identity verification with behavioral analysis to detect identity-associated risk.

**Possible responses**:

* `YES` — signs of fraud associated with this face.
* `INCONCLUSIVE` — no signs of fraud associated with this face.

### Risk Score <a href="#risk-score" id="risk-score"></a>

**Objective**: used together with Identity Verification if its result is "INCONCLUSIVE", generates a probability score to assess whether the user's face matches the holder of the identification document.

**Possible responses**:

* **Positive Score (+10 to +100)**: High probability of being the real holder.
* **Zero Score (0)**: Registration error. A new capture is required.
* **Negative Score (-10 to -100)**: High probability of *not* being the real holder.

| Classification |         Score        |                                                        Recmmendation                                                       |
| :------------: | :------------------: | :------------------------------------------------------------------------------------------------------------------------: |
|    Negative    | Between -40 and -100 |                                           We recommend denying the registration.                                           |
|    Negative    |  Between -10 and -39 |                        We recommend that the client evaluate the risks involved to make a decision.                        |
|     Neutral    |      Zero Score      | We recommend denying the registration and requesting the user to perform a new capture with the actual CPF holder's photo. |
|    Positive    |  Between +10 and +49 |                        We recommend that the client evaluate the risks involved to make a decision.                        |
|    Positive    | Between +50 and +100 |                                          We recommend approving the registration.                                          |

### Validation (1:1) <a href="#validacao-1-1" id="validacao-1-1"></a>

**Objective**: confirm whether the current face is identical to the face used in a reference process.

**Possible responses**:

* `YES` — the face is the same one that was used in the reference process.
* `NO` — the face is not the same one that was used in the reference process.

### Intelligent Revalidation <a href="#revalidacao-inteligente" id="revalidacao-inteligente"></a>

**Objective**: evolution of 1:1 validation, indicated for scenarios where biometrics are not mandatory, combines **metadata** and/or **authenticated passkey** with the biometrics already performed, approving about **70% of cases automatically** and directing the remaining ones to traditional validation by **selfie.**

**Possible responses**:

* `YES` — indicates that the user performing the transaction is the same one who completed the validation in the process used as reference.
* `NO` — indicates that the user performing the transaction is not the same one who completed the process used as reference.

{% hint style="info" %}
This capability is available only through the by Unico integration method.
{% endhint %}

### Reuse and document capture <a href="#captura-e-reaproveitamento-de-documentos" id="captura-e-reaproveitamento-de-documentos"></a>

**Objective**: request, store and reuse documents. We offer the possibility of reusing users' personal documents (*Brazilian passport, CIN, RG and CNH - digital and common*), reducing the friction of this process which usually has high abandonment. And if we do not have the documents in the database, it is possible to capture them.

**Possible responses**:

* **Classification**: indicates which type of document was identified.
* **Data extraction (OCR)**: consists of extracting the document data from an image.
* **FaceMatch**: consists of comparing the selfie face with the document face.
* **CPF Match**: consists of searching the specified document for a given CPF.

### Electronic signature <a href="#assinatura-eletronica" id="assinatura-eletronica"></a>

**Objective**: allow a user to sign digitally using biometrics (selfie), for processes that require a qualified signature.

**Possible responses**:

* Binary of the signed document.

{% hint style="info" %}
This capability is available only through the by Unico integration method.
{% endhint %}

#### Serpro similarity return <a href="#retorno-de-similaridade-da-serpro" id="retorno-de-similaridade-da-serpro"></a>

**Objective**: specific functionality for payroll-deductible credit operations (INSS) or others that require comparison with Serpro's databases.

**Possible responses**:

* **Score between 0-100**: when Serpro finds the face);
* **Score -1**: when Serpro does not find the face;
* **Score -2**: when there is an error in the integration with Serpro and we cannot return the similarity score.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://devcenter.unico.io/unico-idcloud/product-guides/getting-started/capabilities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
