> 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/revenue-streams.md).

# Revenue Streams

Core Revenue StreamsNuri’s revenue streams are diversified to support both short-term growth and long-term sustainability:

**1. Premium Feature Subscriptions**

* Users pay monthly or annually to unlock enhanced features, including:
  * Photo-based food logging and AI meal analysis
  * Voice-enabled wellness tracking (via Whisper)
  * Personalized macro and fitness insights
  * Detailed analytics and recovery suggestions
* Pricing: $9.99/month or $99/year (avg. $8.25/month annually)
* Modeled after leading apps like MyFitnessPal and Noom

**2. Brand Partnerships and Ecosystem Growth**

* Sponsored integrations with health brands, fitness influencers, and supplement companies
* Revenue via:
  * Co-branded fasting/workout challenges
  * Affiliate product placements (e.g., meal kits, wearables, supplements)
  * Feature licensing or API partnerships (e.g., syncing to gym hardware)
* Accelerated post-Q4 2025 with token incentives driving B2B demand

**3. Treasury Management and Staking Yields**

* A portion of $NURI supply allocated to operational reserves
* Revenue via:
  * Liquidity provision and staking yield optimization
  * Strategic token buybacks to reduce supply and increase token utility
* Supports long-term protocol health and user reward loops

| Premium Subscriptions | Recurring user payments for advanced wellness tools | Medium (recurring)  |
| --------------------- | --------------------------------------------------- | ------------------- |
| Brand Partnerships    | Collaborations with wellness brands and platforms   | High (post-Q4 2025) |
| Treasury Yields       | Operational reserves supporting yield & buybacks    | Medium (long-term)  |


---

# 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/revenue-streams.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.