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

# Reading the result

> How to interpret a candidate's score and use it to prioritize your visits.

Each score has three parts: the solvency result, the delinquency result and the confidence tier. Read them together.

## The results

| Result | Values | What it means |
| - | - | - |
| **Solvency** | OK / OK at the limit / KO | Whether the candidate's income can cover the rent. OK at the limit means solvent, but close to the limit. See [Solvency](https://developers.vivara.io/tenant-scoring/how-the-score-works.md#solvency) |
| **Delinquency** | OK / KO / Not checked | Whether the candidate appears in a delinquency register. *Not checked* means you have not sent the ID number yet |

A KO is not a final rejection. It tells you the candidate is a weaker fit for this listing, based on the data you sent.

## The tier

The tier tells you how much to trust the results:

* **Accredited:** the results are based on documented data.
* **Declared:** the results are based on what the candidate told you.
* **Basic:** only solvency is available, based on declared income.

A Declared OK is a good sign, but it depends on the candidate's own statement. An Accredited OK is backed by documents.

## Prioritizing candidates

Vivara recommends the same order it uses for its own visits:

1. **Accredited** candidates, from the lowest effort rate to the highest
2. **Declared** candidates, from the lowest effort rate to the highest
3. Candidates whose effort rate cannot be calculated

Within each tier, a lower effort rate means more room to pay the rent. Accredited candidates come first because their data is backed by documents. This is a recommendation, not a rule: you decide who to call.

## What the score does not tell you

* **Whether the insurer will issue a policy.** The insurer runs its own checks when you ask for a quote and request the policy.
* **Anything about the candidate beyond income and delinquency.** The score does not cover references, rental history or other criteria you may use.

## Deleting a scoring

When you no longer need a scoring, send `DELETE /v1/scorings/{scoringId}` with
your API key. This permanently removes the scoring, its candidatures, saved
assessments and the member personal data stored in that scoring.

A successful deletion returns `204` with no body. Subsequent reads, updates or
deletions return `404` unless you create the scoring again. A scoring that belongs
to another API client also returns `404` and remains unchanged.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.