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

# Business Model

Nuri operates on a freemium business model that leverages AI-driven wellness tools to drive engagement, habit formation, and monetization across three core verticals: wellness, fitness, and nutrition. This approach blends behavior-driven incentives with a premium feature stack that addresses the growing demand for personalized health solutions.

Unlike static wellness apps that monetize only through upfront subscriptions, Nuri integrates Web3 mechanics, token incentives, and contextual AI coaching to build a dynamic, user-driven revenue loop. This hybrid model ensures monetization from both individual users and enterprise-level partners, while maintaining accessibility and reward alignment for the broader user base.


---

# 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://docs.meetnuri.com/business-model.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.
