> For the complete documentation index, see [llms.txt](https://oodlz.gitbook.io/oodlz-gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oodlz.gitbook.io/oodlz-gitbook/company-overview/business.md).
# Business
The OODLZ business model is based on a tri-sided value proposition that benefits Members with a dual cash and yield opportunity and Merchant Partners with brand and loyalty exposure. \
\
This results in a network effect whereby the potential value and utility available to each group – Members and Merchant Partners – increases with the growth of the other. \
\
The growth of Members and Merchant Partners is therefore interrelated, as more Merchant Partners drive Member growth and engagement, and vice versa. \
\
This network effect is critical in scaling OODLZ operating metrics.
The key strength of OODLZ business is that it delivers value for both Members and Merchant Partners.
---
# 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://oodlz.gitbook.io/oodlz-gitbook/company-overview/business.md?ask=&goal=
```
`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.