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

# Media Layer

Pumpkin’s media layer is designed for one purpose: to make live trading credible and scalable.

### Live Streaming (Trading-grade)

Pumpkin supports:

* audio
* video
* screen sharing
* OBS ingest
* multi-host participation (up to 9)
* gifts (single and multi-recipient)
* real-time trading bullet comments

{% @mermaid/diagram content="

flowchart LR
OBS\[OBS Ingest] --> ING\[Ingest Service]
ING --> LL\[Low-Latency Delivery]
HOST\[Hosts/Guests] --> SFU\[WebRTC SFU]
SFU --> LL
LL --> VIEW\[Viewers]
VIEW --> BUS\[Realtime Bus: chat/trades/gifts]" %}

#### Why this matters for live trading

A live trading room is interactive: viewers ask questions, follow trades, watch guests debate, and react instantly. Low-latency and multi-host capacity are core requirements—not optional media features.

### Recording & Replay

Pumpkin records sessions and indexes them with event markers so users can replay the market narrative, not just watch a video.

{% @mermaid/diagram content="flowchart LR
LIVE\[Live Room] --> REC\[Recording Pipeline]
LIVE --> EVT\[Trading + Room Events]
EVT --> IDX\[Marker Indexer]
REC --> REP\[Replay Player]
IDX --> REP" %}

Markers can include:

* strategy publish moments
* entry/exit events
* stop updates
* funding events
* liquidation risk warnings
* major chat highlights


---

# 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.pumpkin.xyz/product/media-layer.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.