> For the complete documentation index, see [llms.txt](https://docs.saas.haut.ai/haut.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saas.haut.ai/haut.ai/developers/saas-api-overview/api-for-face-metrics-2.0/technical-algorithms-results/facial-landmarks.md).

# Facial Landmarks Result Scheme

Result scheme for the Facial Landmarks algorithm in Face Metrics 2.0, which returns a vectorized mask of 53 predefined face points.

Facial landmarks are a set of face points that allow the marking of facial features, such as the nose, mouth, eyes, etc. Haut.AI provides 53 predefined landmark points:

<div align="left"><img src="https://245161714-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MWxBX_zB4FnflOpyBGO%2F-McP1MTGRvmVdtGbiacO%2F-McP5rsNGWS81E6-6Jpn%2Fimage.png?alt=media&amp;token=bccda097-35a9-4e9f-9856-3316c128a387" alt="facial landmarks"></div>

## `algorithm_tech_name`

`facial_landmarks`

## `area_results`

`area_results` is returned as an empty list

## `masks_restored`

The algorithm returns a vectorized mask of the facial landmarks for a restored image

* `"mask_type": "point_mask"`
* `features`

  * geometry

    * `"type": "MultiPoint"`
    * `"coordinates"` list of (x,y,z) landmarks coordinates. The first element of the list corresponds to the point 1 from the image above, the second corresponds to the point 2, etc.

    **NB!** *Note that now z (depth) coordinate returns 0 for all points. This value is reserved for a future update. Use (x,y) coordinates only.*<br>

  See more on Masks [here](/haut.ai/haut.ai-features/algorithms/algorithm-results.md#masks)

## `masks_original`

The algorithm returns a vectorized mask of the facial landmarks for an original image

* `"mask_type": "point_mask"`
* `features`

  * geometry
    * `"type": "MultiPoint"`

  See more on Masks [here](/haut.ai/haut.ai-features/algorithms/algorithm-results.md#masks)

## **Example (JSON)**

{% file src="/files/-McSpxNxuwkzRl1AcSdR" %}
landmarks.json
{% endfile %}

***

{% hint style="warning" %}
Not a Haut.AI client yet?
{% endhint %}

<a href="https://haut.ai/book-a-demo?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button primary" data-icon="user-vneck">Book a demo</a> <a href="https://haut.ai/product/ai-skin-analysis?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button secondary" data-icon="external-link">Platform overview on haut.ai</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.saas.haut.ai/haut.ai/developers/saas-api-overview/api-for-face-metrics-2.0/technical-algorithms-results/facial-landmarks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.