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

# Deepfake API vs Docver

> When to use the standalone Deepfake API and when you need Docver's full identity-verification flow.

Dataspike ships deepfake detection in two products. They overlap on one capability — spotting manipulated media — but solve different problems.

<CardGroup cols={2}>
  <Card title="Deepfake API" icon="fingerprint">
    A single detector. You hand it a file (photo, video, or audio) and it answers one question: **is this fake?** No KYC flow.
  </Card>

  <Card title="Docver" icon="id-card">
    An end-to-end identity-verification flow: **is this a real person, is this their genuine document, and is it really them?**
  </Card>
</CardGroup>

***

## In plain terms

**Deepfake API** is one building block. It doesn't know who is in front of the camera, doesn't match a face against a document, and doesn't check whether the person is live. You drop it into your own process when you only need to catch deepfakes — content moderation, reviewing an interview recording, analyzing a voice message.

**Docver** is a turnkey identity check. During onboarding the user takes a selfie and captures a document, and Docver runs the whole chain at once: it confirms a live person (not a photo, mask, or screen), that the face isn't manipulated, that the document is genuine, and that the selfie matches the document. It's for teams that need full KYC/AML onboarding rather than a standalone detector.

***

## Who it's for

|              | Deepfake API                                       | Docver                          |
| ------------ | -------------------------------------------------- | ------------------------------- |
| **Best for** | HR, proctoring, trust & safety, content moderation | Fintech, crypto, KYC/AML        |
| **Scope**    | Standalone deepfake detector                       | Full identity-verification flow |
| **KYC flow** | No                                                 | Yes                             |

***

## Capability comparison

| Check                            |   Deepfake API   |         Docver         |
| -------------------------------- | :--------------: | :--------------------: |
| Image deepfake                   |         ✅        | ✅ *(in liveness flow)* |
| Video deepfake                   |         ✅        |            —           |
| Audio deepfake / voice cloning   |         ✅        |            —           |
| Liveness & spoofing (PAD)        |         —        |            ✅           |
| Face coverage & quality          |         —        |            ✅           |
| Document deepfake                | ✅ *(standalone)* |      ✅ *(in flow)*     |
| Document spoofing                |         —        |            ✅           |
| Face comparison                  |         —        |            ✅           |
| Metadata / forensic analysis     |         ✅        |            ✅           |
| Async processing (video / audio) |         ✅        |            —           |

<Info>
  Inside Docver, deepfake detection is just one layer — and only on images. The flow runs: **Liveness + Spoofing → Deepfake (selfie) → Face coverage & quality → Document fraud → Document spoofing → Face comparison.**
</Info>