> For the complete documentation index, see [llms.txt](https://metadomo.gitbook.io/metadomo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metadomo.gitbook.io/metadomo-docs/network/user-pipeline.md).

# User Pipeline

Metadomo works through partners to achieve fast market penetration with widest reach of users ready to be onboarded to Web3 as possible. 

<figure><img src="/files/S7672QMJpvs04xH3oE2e" alt=""><figcaption></figcaption></figure>

Metadomo has secured partnerships that enable mass user pipelines through our system:

Gaming:

* Integration with gaming tournament enabler, running on OverWolf which provides game integration through popular MMO games such as Dota 2, CS:GO, Fortnite, LoL, and more, estimated reach of 400M+ MAU.&#x20;

Point Providers

* Pipeline of 100M+ users through China Mobile International, Jegotrip and more.&#x20;

Payment Rails

* Integration with PSPs, payment methods such as WeChat Pay, Alipay, Visa, MasterCard, and more.&#x20;


---

# 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://metadomo.gitbook.io/metadomo-docs/network/user-pipeline.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.