# Transparency

The <mark style="color:green;">**Transparency Dashboard**</mark> gives a real-time, fully on-chain view of platform activity, game performance, and fee allocation. All data comes directly from smart contracts.

<figure><img src="/files/08LC04xlokbxvMIHTXGM" alt="" width="563"><figcaption></figcaption></figure>

#### **Platform Overview Metrics**

These high-level stats summarize the lifetime performance of the Ape Church platform:

* <mark style="color:green;">**Total Volume**</mark> – displays the cumulative amount wagered across all games since launch, measured in APE. This reflects total betting activity and overall platform scale.
* <mark style="color:green;">**House PNL**</mark> – shows the total profit or loss of the House. It also includes the platform’s average RTP (Return to Player), calculated from actual on-chain game outcomes.
* <mark style="color:green;">**Games Played**</mark> – total number of games played across all titles. A direct indicator of platform activity and usage.
* <mark style="color:green;">**Unique Players**</mark> – number of unique wallets that have placed at least one bet. Represents the size of the active on-chain player base.

#### **Game Performance Analysis**

This section allows users to explore performance data for individual games and understand their payout behavior and contribution to overall platform activity.

Each game card includes:

* <mark style="color:green;">**Game Cover Art**</mark> for quick visual identification.
* <mark style="color:green;">**Bet vs Won indicator**</mark>, showing the relationship between total wagered and total payouts.
* A <mark style="color:green;">**“Click for analytics”**</mark> action to access detailed, game-specific on-chain statistics.

This provides a quick overview of how each game performs, with the option to dive deeper into detailed analytics when needed.


---

# 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.ape.church/app-guide/transparency.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.