--- title: Capabilities description: Capabilities are the atomic building blocks of the Unico IDCloud platform — Liveness, Identity Verification, Trust, and more. Each one solves a specific identity check and combines with others inside a flow to deliver a product. canonical: https://developer.unico.io/capabilities locale: en generated_by: markdown-export --- - [/](/) - Capabilities **On this page# Capabilities Reference, not entry pointThis section is a **technical reference**. If you're starting an integration, begin with [Products](/products) — they describe the business problem you want to solve. Capabilities are consulted from there, when you need to understand in detail what each block does and how it responds. ### How capabilities, flows, and products relate​ the problemProductthe recipeFlowthe ingredientsCapabilities **Product** is the business problem: "validate the identity of a new customer in Brazil", "confirm holder identity on a sensitive transaction". **Flow** is the pre-composed combination of capabilities that solves that product. It's the exact value you send in the `flow` field of [Create Process](/developers/api-reference/post-processes). **Capability** is the atomic block — each with its own goal, inputs, and possible responses. This is its reference page. For the full table of which flows exist and which capabilities each one combines, see [Available flows](/developers/start/flows). ### Capability catalog​ CapabilityWhat it solvesIntegration componentsrequired [Liveness](/capabilities/liveness)Verifies that the user is real and alive at the moment of selfie capture.API Web or SDK [Identity Verification](/capabilities/identity-verification)Verifies that the captured face belongs to the holder of the identification document.API Web or SDK [Fraud Risk Classification](/capabilities/fraud-risk-classification)Complements identity verification with behavioral analysis to detect fraud risk.API Web or SDK [Risk Score](/capabilities/risk-score)Probabilistic fraud score, used together with Identity Verification when the result is "inconclusive".API Web or SDK Brazil only [1:1 Validation](/capabilities/1-1-validation)Confirms the current face is the same one used in a reference process.API Web or SDK [Smart Revalidation](/capabilities/smart-revalidation)Orchestrates multiple identity verification methods adaptively, choosing the least-friction approach for each transaction based on available signals.Web or SDK [Document Reuse and Capture](/capabilities/document-reuse-and-capture)Requests, stores, and reuses documents. Reduces friction in journeys with document capture.API Web or SDK [Serpro Similarity Return](/capabilities/serpro-similarity-return)Comparison against the Serpro database — specific to payroll loans (INSS) and similar operations.API Web or SDK Brazil only [RENAPO Verification](/capabilities/renapo-verification)Returns the record RENAPO holds for the user's CURP, alongside the Identity Verification result.API Web or SDK Mexico only [Age Verification](/capabilities/age-verification)Determines whether the person in front of the camera meets the minimum required age, based on biometric analysis.API Web or SDK [Multi Accounts](/capabilities/multi-accounts)Detects whether a face is already linked to another account in the operator's base via 1:N biometric search.API Web or SDK [Cardholder Verification](/capabilities/cardholder-verification)Confirms a card belongs to its declared holder by reusing a previously validated process.API Brazil only Integration surfaces**Web** delivers the journey via iFrame or Redirect (component managed by Unico). **SDK** delivers capture via native SDK (Android, iOS, Flutter). **API** is the headless integration, without the Unico SDK, with your own front-end ([Capture Standard](/developers/sdks-and-tools/capture-standard)) or direct base64 image upload. ### Anatomy of each capability page​ Every capability page follows the same format, to make cross-referencing easier: **What it does** — the capability's goal in a sentence. **Inputs** — what needs to be sent to use it. **Possible responses** — every possible return value and what each one means. **Availability** — supported surfaces (SDK, Web, API). **Valid combinations** — in which flows from the catalog this capability appears. **Products that use this capability** — links back to the Products axis. ### What's next​ **Want to know which flow uses which combination of capabilities?** → [Available flows](/developers/start/flows) **Want to browse the catalog of problems the platform solves?** → [Products](/products) Last updated on Oct 8, 2026**