VU cloud services

Identity APIs you integrate one at a time

VU Cloud Services are four APIs, and each one answers a specific question about a document, a face or a connection. You integrate them into what you already have, without changing providers.

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

  • ID Analysis
  • Face Analysis
  • Antispoofing
  • Connection Fingerprint

Your backend, your orchestration

Browser

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

Who it's for

Add the piece you're missing, without changing what already works.

Each service answers one question and returns something your system can use right away: a verdict, a score, data or signals. They're consumed one at a time, without depending on a full verification flow.

Case 01

You have another provider installed

You don't need to migrate everything to add a capability. You consume only the API you need, in parallel with the provider you already have.

Case 02

Your flow is missing one specific capability

You bring in document reading, face comparison, spoofing detection or connection fingerprinting, without touching your current flow.

Case 03

You're building your own product

You need the pieces, not a platform. You integrate them under your own orchestration and keep control of the rest.

The services

Four APIs, one question each

Each service has its own documentation and its own contract.

ID Analysis

What does this identity document say?

It extracts the data from the front and the back, identifies the document type, crops the face and validates consistency across sides and sources.

Returns
Extracted data and validations
Called by
Your backend
See ID Analysis →
Which one you need

Your question decides the service.

The same guide VU's documentation uses to choose: find your question, and next to it is the API that answers it.

  • ID Analysis

    • What data does this identity document carry?
    • Does the back match the front I was sent?
  • Face Analysis

    • Does the selfie belong to the same person as the document photo?
    • Is this capture good enough for biometrics?
  • Antispoofing Facial

    • Is this face from a real, present person?
    • Was this image generated or manipulated by AI?
  • Connection Fingerprint

    • Has this device been here before?
    • Is the client that claims to use a browser really doing so?
    • Roughly where is this connection coming from?
How they combine

Each one covers a stage of the verification.

An onboarding example, in the documentation's order. The orchestration is yours.

  1. 01Connection Fingerprint

    The fingerprint comes first

    When the session opens, before asking the user for anything. If it looks like a bot, you harden the flow.

  2. 02ID Analysis

    The document is read and validated

    It extracts the data, validates that front and back match and crops the face.

  3. 03Antispoofing · Face Analysis

    The selfie is validated and compared

    It confirms a person is present and compares the selfie with the face on the document.

  4. 04Your backend

    The final decision is yours

    The verdict and the score authorize the approval; the fingerprint and the validations give you the context to decide.

How to start

Self-service: connect these APIs with no middlemen

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

  1. 02

    You confirm accesswith the method the panel offers you

  2. 03

    You open Cloud Servicesin the side menu

  3. 04

    You choose the servicethe one that answers your question

  4. 05

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

  5. 06

    You make your first callwith that service's integration guide

Generate your API Key

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

Frequently asked questions

Yes. Each service is consumed separately, without depending on a full verification flow, and each key corresponds to a single service.
Yes. In an onboarding, each service contributes at a different moment of the same session: the connection fingerprint when it opens, the document analysis next, and finally the validation and comparison of the selfie. You define the order and make the final decision with all the signals.
Identity Link is a complete, managed flow: it validates the document, extracts the data and runs the liveness check in a single process. VU Cloud Services are independent pieces you integrate separately or combined, under your own orchestration.
ID Analysis, Face Analysis and Antispoofing Facial are called from your backend, with your API Key. Never include it in the frontend or in a mobile app. Connection Fingerprint is the exception: the user's browser calls it directly, because the fingerprint is taken from their connection. Your backend then receives the response and verifies its signature.
At docs.vu-one.com you'll find each API's reference, the decision rule, call examples and error handling.

You know what your question is. Now get the API that answers it.

Generate your key and try the service you need.

Generate your API Key

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