> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vu-one.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VU Cloud Services

> The VU APIs you integrate on their own: facial antispoofing and connection fingerprinting. What each one solves, which you need, and how they combine.

<Tip>
  **Available now.** Identity Link Premium and Pro plans create their own api-keys from the **Cloud Services** section of the portal, with no ticket: up to 5 per service, each with 10,000 trial calls. Usage is not billed during the launch period. Connection Fingerprint is contracted through sales and does not use api-keys.
</Tip>

**VU Cloud Services** are APIs you consume one at a time, without depending on a full verification flow. Each one answers a specific question and returns something your system can act on immediately.

<CardGroup cols={2}>
  <Card title="ID Analysis" icon="id-card" href="/en/vucs/id-analysis/introduction">
    What does this identity document say? Extracts the data from the front and the back, identifies the document type, crops the face, and validates consistency between sides and sources.

    **Front and back, with cross-validations.**
  </Card>

  <Card title="Face Analysis" icon="user-check" href="/en/vucs/face-analysis/introduction">
    Is it the same person? Compares the selfie against the document photo — or a stored vector — and scores capture quality, pose, and facial attributes.

    **A 0–100 score for every pair of faces.**
  </Card>

  <Card title="Facial Antispoofing" icon="face-viewfinder" href="/en/vucs/antispoofing-face/introduction">
    Did this selfie come from a real person in front of the camera? Detects photocopies, screenshots, deepfakes, and chromatic tampering.

    **One HTTP call, one verdict.**
  </Card>

  <Card title="Connection Fingerprint" icon="fingerprint" href="/en/vucs/connection-fingerprint/introduction">
    Who is on the other end of the connection? Identifies the device by its TLS signature, its headers, and its geographic origin.

    **No SDK, no tracking JavaScript.**
  </Card>
</CardGroup>

## Which one you need

| If your question is… | The service is |
| - | - |
| What data does this identity document carry? | **ID Analysis** |
| Does the back match the front I was sent? | **ID Analysis** |
| Is the selfie the same person as the document photo? | **Face Analysis** |
| Is this capture good enough for biometrics? | **Face Analysis** |
| Is this face a real, present person? | **Facial Antispoofing** |
| Was this image generated or manipulated by AI? | **Facial Antispoofing** |
| Has this device been here before? | **Connection Fingerprint** |
| Is the client that claims to be a browser really one? | **Connection Fingerprint** |
| Roughly where does this connection come from? | **Connection Fingerprint** |

## How they differ

| | ID Analysis | Face Analysis | Facial Antispoofing | Connection Fingerprint |
| - | - | - | - | - |
| What it analyzes | The document photos | One or more face images | An image you send | The TLS connection of the caller |
| What it returns | Extracted **data** and validations | A 0–100 **score** in `biometric` | A **verdict** in `spoofing` | **Signals** for your risk engine |
| Who makes the call | Your backend | Your backend | Your backend | The end user's browser |
| Authentication | `Api-Key` header | `Api-Key` header | `Api-Key` header | None on the main endpoint |
| Base URL | Provided by VU per environment | Provided by VU per environment | Provided by VU per environment | `https://fingerprint.api.vusecurity.com` |
| Integrity | Server to server | Server to server | Server to server | RSA signature you verify |

<Note>
  The underlying difference is who sets the threshold: **Facial Antispoofing decides** (`spoofing` is a verdict), **ID Analysis and Face Analysis return data and scores** over which your policy defines what to accept, and **Connection Fingerprint informs** — inputs for your own risk engine.
</Note>

## How they combine

In a real onboarding, all four contribute at different moments of the same session: the document is read first, the document face is compared against the selfie, and the selfie goes through liveness.

```mermaid theme={null}
sequenceDiagram
    participant B as Browser
    participant S as Your backend
    participant CF as Connection Fingerprint
    participant IDA as ID Analysis
    participant FA as Face Analysis
    participant AS as Facial Antispoofing
    B->>CF: GET / when the session opens
    CF-->>B: userData + signature
    B->>S: Forwards the full fingerprint
    B->>S: Document photos
    S->>IDA: POST /front → POST /back
    IDA-->>S: data + document face
    B->>S: Captured selfie
    S->>AS: POST /inference
    AS-->>S: spoofing: false
    S->>FA: POST /inference (selfie vs document face)
    FA-->>S: biometric ≥ 70
    S->>S: Decides with all the signals
```

<Steps>
  <Step title="The fingerprint arrives first">
    You get it when the session opens, before asking the user for anything. If the client already looks automated, you can harden the flow or stop it without spending a biometric check.
  </Step>

  <Step title="The document is read and validated">
    [ID Analysis](/en/vucs/id-analysis/introduction) extracts the data from the front and the back, validates that both sides belong to the same document, and returns the cropped face.
  </Step>

  <Step title="The selfie is compared and checked for liveness">
    [Facial Antispoofing](/en/vucs/antispoofing-face/introduction) confirms the selfie came from a present person; [Face Analysis](/en/vucs/face-analysis/introduction) compares it against the document face: `biometric["0"]["1"] >= 70`.
  </Step>

  <Step title="The final decision is yours">
    The antispoofing verdict and the biometric score authorize approval; the fingerprint and the document validations tell you with how much confidence, and whether an extra factor is worth asking for.
  </Step>
</Steps>

## Before you start

<CardGroup cols={2}>
  <Card title="Credentials and environments" icon="key">
    VU provides the base URL and api-key for ID Analysis, Face Analysis and Facial Antispoofing per environment — each service has its own key. For Connection Fingerprint, your origins must be registered in the CORS allowlist before the first call.
  </Card>

  <Card title="Support" icon="life-ring">
    Write to [customer.support@vusecurity.com](mailto:customer.support@vusecurity.com) with the transaction identifier, the environment, and the approximate timestamp.
  </Card>
</CardGroup>

<Warning>
  None of these services replaces [Identity Link](/en/identity-link/introduction) when you need a full identity verification — document, extracted data, and liveness in a single managed flow. They are building blocks that integrate on their own or combined under your own orchestration.
</Warning>


## Related topics

- [Identity Link API Changelog](/en/identity-link/changelog.md)
- [VU Technical Documentation](/en/index.md)
- [Errors and diagnostics](/en/vucs/id-analysis/errors.md)
- [Interpreting responses](/en/vucs/face-analysis/responses.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.