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

# Plugins

- [Api Integration Plugins](https://docs.curedao.org/plugins/api-integration-plugins.md)
- [Data Analysis Plugins](https://docs.curedao.org/plugins/data-analysis-plugins.md)
- [Data Collection Plugins](https://docs.curedao.org/plugins/data-collection-plugins.md): Data collection can be done using wearable sensors, third-party applications, and client applications.
- [Observational Studies Plugin](https://docs.curedao.org/plugins/observational-studies-plugin.md): We’ve collected over 10 million data points on symptom severity and influencing factors from over 10,000 people.
- [OpenCures Trial Management Plugin](https://docs.curedao.org/plugins/open-cures-trial-management-plugin.md)
- [Optomitron Real-Time Decision Support Plugin](https://docs.curedao.org/plugins/optomitron-real-time-notifications-plugin.md): Optomitron is an AI assistant that analyzes your data discover which hidden factors are most likely to worsen or improve inflammatory symptom severity.
- [Outcome Labels Plugin](https://docs.curedao.org/plugins/outcome-labels-plugin.md)
- [Root Cause Analysis Plugin](https://docs.curedao.org/plugins/root-cause-analysis-plugin.md): Reports are intended to help you and your physician to gain insight into the root causes and effective solutions to help you minimize your symptoms.
- [Predictor Search Engine Plugin](https://docs.curedao.org/plugins/predictor-search-engine-plugin.md)


---

# 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://docs.curedao.org/plugins.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.