> For the complete documentation index, see [llms.txt](https://docs.thryve.health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thryve.health/getting-started/introduction.md).

# Introduction

Welcome to Thryve! We help you to access data from 500+ wearable devices and health apps through one integration.

{% hint style="info" %}
Check out the full list of [data sources](https://docs.thryve.health/thryve-data-sources/overview) and [data types](https://docs.thryve.health/thryve-product-overview/access/data-types-biomarker)  that we support.
{% endhint %}

Thryve enables app developers to access fitness and health data from smartwatches, smartphones, medical devices, health sensors, and health apps via one unified integration. 

Thryve's technology allows you to obtain authorization to get data within your existing web or mobile app. We will ensure you always have the latest information on your users' activities and health.

The following pages explain the main concepts and will help you to:

* [**Connect**](/thryve-product-overview/connect.md) your users' wearables with your app, ensuring health data is flowing in near-time 24/7
* [**Access**](/thryve-product-overview/access/data-types-biomarker.md) new data and historical data for hundreds of health data sources in a well-structured format
* [**Understand**](/thryve-product-overview/understand.md) your users' health by leveraging Thryve's data annotations and on-top analytics
* [**Control**](/thryve-product-overview/control.md) all aspects of your users' experience and all data processing<br>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thryve.health/getting-started/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.