> 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/releases/changelog/skin-saas-algorithms-updates.md).

# Skin SaaS algorithms updates

Quality algorithm update and Skintone Classification release

<figure><img src="https://245161714-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWxBX_zB4FnflOpyBGO%2Fuploads%2FNyKLfywVz6j3xfTWMm9O%2FFrame%207352%20(1).png?alt=media&amp;token=7c20702d-d864-4e03-a11c-73dc3cf953cc" alt=""><figcaption></figcaption></figure>

## Quality algorithm update

**Attention to API users:** Quality Algorithm update is coming in 30 days.

**What will change?** The update is focused on making the output more clear and detailed. The update affects submetrics and feedback outputs of the algorithm. Read more below ⬇️

**No actions are required if you:**

* Only use a B2C app constructor;
* Only use the main metric output.

### Upcoming changes

#### Submetrics

| Before                                                                                                                     | After                                                                                                                                                                                                                                                                                                 |
| -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Previously, submetrics were included as *key-value pairs (name: value)* in a separate field *`QualityResult.sub_metrics.`* | <p>Now, the submetrics’ output has the same structure as the other algorithms’ output in Face Metrics 2.0.</p><p>They are now included as a <em>list of Metrics (with value, tech\_name and widget\_type fields)</em> in <em><code>QualityResult.area\_results\[0].sub\_metrics</code></em> field</p> |

Submetrics were also redesigned to better reflect image quality properties for the end-user:

1. The **“detection”** submetric was **removed**;
2. To replace the “detection” submetric, **two new submetrics were introduced: “full\_face\_score”** - the degree of face presence and **“occlusion\_score”** - the degree of skin areas occlusion.
3. **A new submetric “shadows\_score”** is added that indicates the degree of the skin illumination uniformness and the presence of shadows.

#### Feedback

| Before                                                                                                               | After                                                                                                                                                                                                                                                                                                                                   |
| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Previously, feedback was included as *key-value pairs (name: value)* in a separate field *`QualityResult.feedback.`* | <p>Feedback -> Problems\*<br><br>“Problems” output is designed to better reflect image quality issues for the end-user. Problems are presented as a list of <em>short codename strings</em> in a new field <em><code>QualityResult.problems.</code></em><br><br>\*The old field named “feedback” is deprecated and will be removed.</p> |

All details regarding the update can be found in[ our documentation.](https://docs.saas.haut.ai/developers/developer-guides/face-application/version-2.0/image-quality-1)

Please contact us via the support desk if you have any further questions.

## Skin Tone Classification

The new skintone classification algorithm has a more clear output than the old Skintone algorithm.

Skintione Classification algorithm analyses how tan the skin is and returns the result as one of the 6 values:

1. Very light - very light skin tone
2. Light- light skin tone
3. Intermediate - intermediate skin tone
4. Tan - tan skin tone
5. Brown- brown skin tone
6. Dark - dark skin tone

Read more about the new algorithm in [our documentation.](https://haut-ai-1.gitbook.io/haut.ai/developers/developer-guides/face-application/version-2.0/skintone_classification)

## Other improvements

✨ We are constantly improving our algorithms and in 30 days we are going to release a new version of the perceived age algorithm!

It is trained on more data and gives more precise results!

***

{% 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/releases/changelog/skin-saas-algorithms-updates.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.
