> For the complete documentation index, see [llms.txt](https://trywink.gitbook.io/wink/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trywink.gitbook.io/wink/product/messenger.md).

# Messenger

Verified users can direct message with creators. Fans can send tips in USDC or gifts with instant payout to creator, they can also send media files such as photos or videos.

### Features

* **Membership filter:** Creators can filter chats based on membership type to selectively respond to paying supporters
* **Broadcast message:** Creators can broadcast message to all their followers or members
* **Pay-per-view (PPV) Content:** Creators can send content that can be unlocked by paying
* **Tipping:** Creators can set up a pricing menu in their bios, allowing fans to pay directly for perks like custom videos via tips
* **\[Coming Soon] Gifts**: Fans can send tips in the form of virtual gifts. E.g. :bouquet::race\_car::house:

### PPV & tips fee structure

Creators pay 20% on completed PPV (Pay-per-view) sales and 10% platform fee from tips received through Messenger


---

# 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://trywink.gitbook.io/wink/product/messenger.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.