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

# About Multiplier

### The Onchain Liquidity Router

Multiplier is infrastructure for converting attention into programmable token demand. We provide the rails where entertainment surfaces become liquidity routers, and every interaction creates verifiable market flow.

### How It Works

**The Core Mechanism**

<p align="center">Player wagers → Risk Engine → Order Router (DEX/AMM with slippage guards) → Onchain Proof → Curation &#x26; Auctions</p>

Every wager becomes a live market buy. Winners receive token positions directly. Communities compete for flow allocation through transparent auctions. The entire system operates onchain with verifiable receipts.

### Three Key Primitives

* **Router** – The execution layer that converts wagers into DEX orders with optimal routing and slippage protection.
* **Allocation** – Auction system where communities bid for curation slots to capture platform-generated orderflow.
* **Surfaces** – Fungible formats (games, creator tools, SDK integrations) that capture attention and feed the router.

<figure><img src="https://3941755903-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL0ZnSUScP3moHqDZTuE2%2Fuploads%2FqpPbcQhFXNDowdYEdbmF%2Fimage.png?alt=media&amp;token=946145c9-759f-4e1a-9987-fcae311f3d13" alt=""><figcaption></figcaption></figure>

### The Infrastructure Play

We're not just a gaming platform, we're building the pipes for Gamified Capital Markets. Games are simply the first surface demonstrating what's possible when you turn engagement into orderflow.

The enduring asset is the liquidity rail itself: a programmable, verifiable system that any partner can plug into. Wallets, launchpads, creators, and protocols can all become liquidity routers through our infrastructure. \
Tokens will be the first long tail asset we will be injecting liquidity into, other convex upside assets such as prediction markets, RWAs & liquidity positions are all possible to be integrated with.&#x20;

### What We Enable

* **For Players**: High-variance games with real token upside and visible market impact
* **For Communities**: Measurable conversion from attention to holder acquisition
* **For Developers**: Revenue-generating campaigns that tap into existing liquidity infrastructure

### Coming Soon

* Token driven community curation
* Self-service SDK for third-party developers
* Creator tools for embedded market mechanics

Multiplier: Infrastructure for the attention-to-liquidity pipeline. Where every surface becomes a router, and every interaction moves markets.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.multiplier.fun/about-multiplier.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
