> For the complete documentation index, see [llms.txt](https://developer.salesintel.io/salesintel-api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.salesintel.io/salesintel-api-documentation/getting-started-with-salesintel-apis/use-cases/a-note-on-data-quality-tiers.md).

# A Note on Data Quality Tiers

SalesIntel exposes two tiers of data via our APIs - human-verified and machine-verified. Human-verified data has each data point assessed by our researches. Machine-verified data is based on layering signals and data science. Both tiers of data are valuable for different purposes. Please connect with the SalesIntel team about your use case and we can advise when to use what data.

All of the APIs allow for filtering of quality tiers based on the `verified` parameter, which can be helpful based on what you are trying to accomplish and can help eliminate overlap or duplication between records. Your contract may support different rates between different tiers of data, as well.


---

# 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://developer.salesintel.io/salesintel-api-documentation/getting-started-with-salesintel-apis/use-cases/a-note-on-data-quality-tiers.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.