> For the complete documentation index, see [llms.txt](https://api-docs.speechace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.speechace.com/api-reference/score-text-pronunciation/handling-word-scores.md).

# Handling word scores

The **word-level quality score** helps you assess the pronunciation accuracy of a specific word within a sentence. This score provides insight into how well that particular word was pronounced compared to the expected standard.

<div align="left"><figure><img src="/files/zdgOlhP9DLGzsL4VQeHV" alt="" width="291"><figcaption></figcaption></figure></div>

{% hint style="info" %}
The scale of the quality score can be interpreted from the scoring [guide](/guides-on-common-topics/intepreting-quality-score.md).
{% endhint %}

You can use the `quality_score` at the word level to display the analysis of the spoken response in your app using the following [color codes](/guides-on-common-topics/intepreting-quality-score.md):

<table><thead><tr><th width="118">Score</th><th width="95">Color</th><th>Description</th></tr></thead><tbody><tr><td>90 - 100</td><td>Green</td><td>Excellent. Native or native-like</td></tr><tr><td>80 - 90</td><td>Green</td><td>Very Good and clearly intelligible.</td></tr><tr><td>70 - 80</td><td>Orange</td><td>Good. Intelligible but with one or two evident mistakes.</td></tr><tr><td>60 - 70</td><td>Red</td><td>Fair. Possibly not intelligible with several evident mistakes.</td></tr><tr><td>0 - 60</td><td>Red</td><td>Poor and must be reattempted.</td></tr></tbody></table>

For example, in the case shown below, the `quality_score` for the word "walk" is 65. Consequently, it is displayed in <mark style="color:red;">**RED**</mark> in the question based on the test-taker's response, indicating several evident mistakes in pronunciation.


---

# 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://api-docs.speechace.com/api-reference/score-text-pronunciation/handling-word-scores.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.