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

# Welcome

> #### Brands should earn the loyalty of their customers, not the other way around.

Fandom (FNDM) is a gamified rewards platform for the travel sector that finally creates “win-win” situations for both Loyalty Brands **and Travelers**. \
\
For Travel Brands, FNDM enables the expansion of existing Loyalty Programs by building deeper, trust-based relationships centered around gameplay, and having fun. 

For Travelers, FNDM facilitates the sharing and monetization of their data to Loyalty Travel Brands through Blockchain Smart Contracts that pay the customer for their [**Zero-Party Data**](https://www.forrester.com/report/QA-What-Marketers-Need-To-Know-About-ZeroParty-Data/RES145095).

Become a Fan of FNDM today by registering your interest in the Pre-Sale Round using the link below.

{% embed url="<https://fndm.app>" %}


---

# 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://wp.fndm.app/readme.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.