> ## Documentation Index
> Fetch the complete documentation index at: https://peak-docs.birdeye.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Object + Command Architecture

> The foundational model behind every screen in Birdeye Peak.

<Note>
  Every screen in Peak is the combination of an **Object** and a **Command**. Once you understand this pairing, the entire product becomes predictable.
</Note>

## The two halves of every view

Peak organizes all of its data around two concepts:

* An **Object** is the entity you want to analyze — a token, a protocol, a wallet, a network.
* A **Command** is the analytical view applied to that Object — a description page, a performance breakdown, a holder analysis.

You always specify both. The Object answers *what* you are looking at. The Command answers *how* you are looking at it.

## A concrete example

Consider the view `SOL TKD`:

* **`SOL`** is the Object — the Solana token.
* **`TKD`** is the Command — Token Description, a summary view that includes key attributes, supply, market data, and links to related analyses.

Switch the Command and you change the analytical angle on the same Object:

* `SOL TKE` — Tokenomics for Solana
* `SOL OWN` — Ownership and holder concentration for Solana
* `SOL LTD` — Live trade stream for Solana

Switch the Object and you keep the same analytical angle on a different entity:

* `ETH TKD` — Token Description for Ethereum
* `Uniswap PRA` — Protocol Analysis for Uniswap

This consistency is intentional. The vocabulary stays the same regardless of which Object you are working with.

## Why this model

Most crypto analytics tools blend pages together inconsistently — one screen mixes price, holders, and tokenomics; another splits them differently. The result is that every new screen requires re-learning the layout.

Peak's Object + Command model solves this by making every analytical view a deliberate, named unit. You learn the Commands once, and they apply across every Object of the same type.

For institutional users running the same analysis across many entities, this reduces the cognitive overhead of navigation to near zero.

## How Commands are organized

Commands within an Object are grouped by purpose. For example, the Token Object includes Commands grouped under:

* **Token Overview** — descriptive and structural information (`TKD`, `TKE`, `OWN`, `MTM`)
* **Price** — price action and technical views (`PMN`)
* **Trading Statistic** — activity, liquidity, and trader behavior (`PFA`, `LTD`, `MLA`, `CWT`)

These groups appear in the Object's full command catalog. See [Commands](/docs/core-concepts/commands/overview) for the complete reference.

## Command naming conventions

Every Command has:

* A **full name** — e.g. *Token Description*, *DEX Performance*
* A **three-letter abbreviation** — e.g. `TKD`, `DEP`

The abbreviation is what you type to reach the view quickly. It also appears in:

* The header pill when the command is active
* Cross-reference links in content
* The Suggested Commands footer
* Search results

<Tip>
  The three-letter format is borrowed from financial terminals. It is intentionally short so that experienced users can navigate by typing rather than clicking.
</Tip>

## Object-less Commands

A small number of Commands operate across all instances of an Object type rather than a single one. These are called **Object-less Commands**.

Examples:

* `ATK` — All Tokens. A screener across the entire token universe.
* `APT` — All Protocols. A screener across all indexed protocols.

Object-less Commands are the starting point when you want to discover or filter, rather than analyze a specific entity. See [Object-less Commands](/docs/core-concepts/commands/object-less-commands) for the full list.

## The standard shell

Every Command, whether scoped to an Object or Object-less, renders inside the same shell:

| Element                   | Location            | Purpose                                              |
| ------------------------- | ------------------- | ---------------------------------------------------- |
| Header bar                | Top                 | Search, Object selector, Command pill, market ticker |
| L1 tabs                   | Below header        | Major sections within the Command                    |
| L2 sub-tabs               | Below L1 (optional) | Subdivisions inside an L1 tab                        |
| Content area              | Main body           | Tables, charts, stat cards                           |
| Suggested Commands footer | Bottom              | Contextual related Commands                          |

This consistency means once you learn one Command's layout, you understand the structure of every Command in Peak.

## Next steps

<CardGroup cols={2}>
  <Card title="Navigating Peak" icon="compass" href="/docs/core-concepts/mental-model/navigating-peak">
    Learn how to move between Objects and Commands efficiently.
  </Card>

  <Card title="Cross-references & Workflows" icon="arrows-cross" href="/docs/core-concepts/mental-model/cross-references-workflows">
    Understand how Peak links related views into research workflows.
  </Card>
</CardGroup>