> For the complete documentation index, see [llms.txt](https://saviorofhealth.gitbook.io/saviorofhealth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saviorofhealth.gitbook.io/saviorofhealth-docs/overview/summary.md).

# 1. Summary

{% hint style="warning" %}
This page is part of a draft under legal review. It contains **\[TBD]** items the team has not yet confirmed. See the [Important Notice](https://saviorofhealth.gitbook.io/saviorofhealth-docs/legal/notice.md) for what each marker means.
{% endhint %}

{% hint style="warning" %}
Savior of Health (the "**Platform**") is consented health-data infrastructure: organisations (clinics, researchers, and brands) commission surveys and receive threshold-suppressed statistical outputs through a Partner Portal and a metered Data API. The supply side is a live consumer health application at saviorofhealth.app, where members keep a daily health journal, talk to four AI health agents that read the member's own record before answering, and answer short health surveys. No revenue is recorded in the Platform database (Section 3); revenue outside the database is **\[TBD]**.
{% endhint %}

Members receive **Heal Points (HP)** for activity on the Platform, including for certain public promotion of the Platform on social media (Section 7). HP are an off-chain reward unit recorded in the Platform database. HP have no monetary value, cannot be redeemed, withdrawn, cashed out, or transferred, and confer no right to any other asset.

The Platform has been targeted by large-scale automated registration. As of 19 October 2026, **80.5% of registered accounts are classified as automated** (Section 6).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://saviorofhealth.gitbook.io/saviorofhealth-docs/overview/summary.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 `automate deployments from our CI pipeline` 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.
