# by Unico vs by Client
## When to use each model
| by Unico | by Client |
| :-----------------------------------------------------------------------------------------------------------------------: | :----------------------------------------------------------------------------------------------------: |
| Ideal when you want to outsource the complete validation journey. | Ideal when you need greater visual control and user experience. |
| You only send the user's identification document number; Unico handles the interface, data capture, UX flow and security. | You already capture selfie / data on the client (*app/web*) or via SDK. |
| You will receive a **link** for the end user to complete the flow. | Unico processes only the backend and analysis part.
|
## Overview and Comparison
It is possible to integrate with the Unico IDCloud platform through two integration methods: **by Unico** and **by Client**. Understand below the main differences between them.
{% hint style="info" %}
Use this table to quickly identify which model best fits your scenario.
{% endhint %}
| Criterion | by Unico | by Client |
| :---------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| **User journey** | Managed by Unico. | Managed by the client (*local UI or Unico SDK*). |
| **Input data** | You create the process **only** with the number of the **user's identification document**+ **flow** with capabilities that it will use. | You create the process with the **user's identification document number** + **selfie in base64** (*or in JWT if you use Unico's SDK*). |
| **Output data** | The service **returns a link** in the API response, which can be sent to the user via **WhatsApp/SMS** OR **rendered** in your application. | The service returns in the **response** the payload of the performed validation. |
| **Response type** | Validation is **asynchronous**, that is, when generating the link and making it available to the end user, it is necessary to **wait for them to complete the journey**, then, **fetch through a GET endpoint** the process response. | Validation is **synchronous** for almost all capabilities - **except** for the Risk Score (*if there is a derivation to the Risk Score, it will be necessary to use the GET endpoint to obtain the final response*). |
| **Weebhooks** | **Highly recommended** the use of webhooks to consume the final response at the end of the user's journey (*polling is possible, but less recommended*). | Synchronous response for approximately 80-90% of cases, requiring the use of webhook and/or polling for the remaining percentage.
|
## Available Capabilities
| Capabilities | by Unico | by Client |
|---|
| Identity Verification |  | |
| Risk Score | | |
| Behavior Alert | | |
| Liveness | | |
| Validation (1:1) | | |
| Smart Revalidation | |  |
| Reuse and Document Capture | | |
| Electric Signature | | |
| Serpro similarity return | | |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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/by-unico-vs-by-client.md?ask=
```
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.