# 3d visualizer

A three-dimensional wave surface rendering of the order book. Found in the Depth panel's 3D tab.

## What It Shows

The 3D visualization maps the order book into a surface where:

| Axis           | Dimension | Meaning                                      |
| -------------- | --------- | -------------------------------------------- |
| **X**          | Price     | Price levels from 0% to 100%                 |
| **Y**          | Time      | Historical snapshots of the order book       |
| **Z** (height) | Volume    | Amount of liquidity at each price/time point |

## Color Legend

Colors map to volume intensity:

| Color                | Meaning                     |
| -------------------- | --------------------------- |
| **Cool blue/purple** | Low volume (thin liquidity) |
| **Green**            | Moderate volume             |
| **Yellow/orange**    | High volume                 |
| **Red/white**        | Very high volume (walls)    |

## Controls

* **Rotate**: Click and drag to rotate the 3D view
* **Zoom**: Scroll wheel to zoom in/out
* **Pan**: Right-click and drag to pan

## Reading the Surface

### Liquidity Walls

Tall ridges on the surface represent large order concentrations at specific price levels. These act as support (bid walls) or resistance (ask walls).

### Spread Canyon

The gap between bid and ask sides appears as a valley in the center of the surface. Wider valleys indicate wider spreads and higher taker cost.

### Temporal Patterns

The Y-axis (time) shows how the order book evolves. If a wall builds over time, it represents persistent support/resistance. If it appears suddenly, it may be a temporary large order.

### Symmetry

A roughly symmetric surface (equal depth on bid and ask) suggests balanced market sentiment. Asymmetry (deeper on one side) suggests directional pressure.

## Data Sources

The 3D visualizer uses the same order book data as the Book tab, fetched from the CLOB API via the `/clob/` proxy. The surface is constructed from snapshots of the order book at different time intervals.

{% hint style="info" %}

### Performance

The 3D rendering uses WebGL. On lower-powered devices, you may experience reduced frame rates. The visualization automatically reduces polygon count on mobile and low-end hardware.
{% endhint %}


---

# 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://yesno-1.gitbook.io/yesno-docs/methodology/3d-visualizer.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.