# Creator Games

Multiplier isn’t just for players, it’s an **open entertainment liquidity layer**. Creators, studios, and developers can build on top of our infrastructure to bring their own games and experiences into the Multiplier ecosystem.

When your game integrates Multiplier, every play isn’t just engagement.

It’s **real market demand routed into tokens.**

***

### Build With Multiplier

* **Monetize Attention** – Every round of gameplay triggers live token purchases.
* **Plug Into Liquidity** – Route your users directly into curated tokens with buy pressure.
* **Grow Communities** – Games become distribution rails for tokens and creators.

***

### APIs & SDKs (Coming Soon)

We’re building out **developer-first tooling** to make integration simple and scalable:

* **APIs** for liquidity routing, token curation, and on-chain receipts.
* **SDKs** for plug-and-play game mechanics, tokenized rewards, and user progression.
* **Dev Dashboard** for analytics, campaign management, and community tracking.

***

### Get Involved Early

If you’re a:

* Game studio looking to launch on-chain titles,
* Creator with an audience and brand, or
* Token project wanting to distribute through gameplay...

👉 Reach out to us. Early partners will get priority access to APIs, SDKs, and integration support as we roll out the full builder stack.

***

Multiplier isn’t just a platform — it’s a **new distribution channel**. Let’s build the next generation of onchain entertainment together.


---

# Agent Instructions: 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:

```
GET https://docs.multiplier.fun/games/creator-games.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
