> For the complete documentation index, see [llms.txt](https://doc.ozforensics.com/oz-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ozforensics.com/oz-knowledge/guides/developer-guide/api/oz-api/types-of-analyses-and-what-they-check.md).
# Types of Analyses and What They Check
Here, you'll get acquainted with types of analyses that Oz API provides and will learn how to interpret the output.
Using Oz API, you can perform one of the following analyses:
* [biometry](#biometry),
* [quality (liveness, best shot)](#quality-liveness-best-shot),
* [documents](#documents) (deprecated),
* [collection (1:N)](#blacklist).
## Biometry
The Biometry algorithm allows comparing several media and check if the people on them are the same person or not. As sources, you can use images, videos, and scans of documents (with photo). To perform the analysis, the algorithm requires at least two media (for details, please refer to [Rules of Assigning Analyses](/oz-knowledge/guides/developer-guide/api/oz-api/rules-of-assigning-analyses.md)).
Results overview
* SUCCESS – everything went fine, the analysis has completed successfully;
* DECLINED – the check failed (an attack detected).
If the analysis hasn't been finished yet, the result can be PROCESSING (the analysis is in progress) / FAILED (the analysis failed due to some error and couldn't get finished).
If you have analyzed multiple media, the aggregated status will be SUCCESS only if each analysis on each media has finished with the SUCCESS result.
## Quality (Liveness, Best Shot)
The Liveness detection (Quality) algorithm aims to check whether a person in a media is a real human acting in good faith, not a fake of any kind.
The Best Shot algorithm checks for the best shot from a video (a best-quality frame where the face is seen the most properly). It is an addition to liveness.
Results overview
* SUCCESS – everything went fine, the analysis has completed successfully;
* DECLINED – the check failed (an attack detected).
If the analysis hasn't been finished yet, the result can be PROCESSING (the analysis is in progress) / FAILED (the analysis failed due to some error and couldn't get finished).
If you have analyzed multiple media, the aggregated status will be SUCCESS only if each analysis on each media has finished with the SUCCESS result.
## Documents
{% hint style="danger" %}
Starting July 1, 2027, the Documents analysis will no longer be available.
{% endhint %}
The Documents analysis aims to recognize the document and check if its fields are correct according to its type.
{% hint style="info" %}
*Oz API uses a third-party OCR analysis service provided by our partner. If you want to change this service to another one, please* [*contact us*](mailto:Info@ozforensics.com)*.*
{% endhint %}
As an output, you'll get a list of document fields with recognition results for each field and a result of checking that can be:
* The documents passed the check successfully,
* The documents failed to pass the check.
Additionally, the result of Biometry check is displayed.
## Collection (1:N)
The Collection checking algorithm is used to determine whether the person on a photo or video is present in the database of pre-uploaded images. The person's face is being compared with the faces of known swindlers or a list of VIPs depending on your needs.
Results overview
* SUCCESS – everything went fine, the analysis has completed successfully;
* DECLINED – the check failed (an attack detected).
If the analysis hasn't been finished yet, the result can be PROCESSING (the analysis is in progress) / FAILED (the analysis failed due to some error and couldn't get finished).
If you have analyzed multiple media, the aggregated status will be SUCCESS only if each analysis on each media has finished with the SUCCESS result.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.ozforensics.com/oz-knowledge/guides/developer-guide/api/oz-api/types-of-analyses-and-what-they-check.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.