> For the complete documentation index, see [llms.txt](https://4heal.gitbook.io/4heal-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4heal.gitbook.io/4heal-1/introduction/what-4heal-solves.md).

# What 4Heal Solves

## 4Heal’s Positioning: Depin × Health Intelligence × Health Concierge

4Heal’s goal is not to launch yet another health app, but to build:

> **An AI health concierge that continuously understands your body, provides actionable recommendations, and evolves alongside your lifestyle.**

It is composed of multiple capability layers:

* Wearable devices
* Health data
* Behavior feedback
* Reasoning & modeling systems
* A value network

Together, these form a health intelligence agent that can:

* Continuously understand individual physical changes;
* Provide tailored health actions;
* And keep improving itself over time.

For 4Heal:

* **Wearables** are the **entry point** to the real world;
* **Health data** is the **bridge** for understanding the body;
* The **Depin network** is the value transmission layer;
* The **reasoning and modeling layer** is the **core engine** of the entire system.

The goal of this system is **not** to replace any single device or to build a closed ecosystem

but to create an **open, extensible health intelligence system** that can continuously absorb new devices, data sources, and capabilities.

***


---

# 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://4heal.gitbook.io/4heal-1/introduction/what-4heal-solves.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.