> For the complete documentation index, see [llms.txt](https://whitepaper.valley22.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.valley22.xyz/valley22-by-karma-labs/consumer-ecosystem.md).

# Consumer Ecosystem

Karma's consumer ecosystem consists of three parts to form a customer-centered experience that enhances the customer/merchant experience.

* **Consumer**: In our customer-centered consumer experience, customers can build their reputation through member tokens from merchants, experience member-only services, discounts and receive exclusive information from merchants while also being able to benefit and trade these experiences to others.
* **Merchant**: Merchants can endow membership rights to their targeted audiences. Based on consumer behavior, merchants can build closer connections with customers by providing enhanced experiences tailored to their best customers.
* **Lending platform**: Customers own their own member rights in the consumer ecosystems, their members token can be borrowed on lending platform.


---

# 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://whitepaper.valley22.xyz/valley22-by-karma-labs/consumer-ecosystem.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.
