> ## 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.

# For Research Analysts

> How research analysts use Peak to produce deep dives and sector analysis.

This guide outlines how research analysts use Peak to investigate tokens, protocols, and sectors. The emphasis is on depth and rigor rather than speed — Peak consolidates the data typically gathered across multiple sources into a single workspace.

## What Peak supports for analysts

<CardGroup cols={2}>
  <Card title="Single-asset deep dives" icon="layer-group">
    Examine an Object from every relevant analytical angle.
  </Card>

  <Card title="Comparative analysis" icon="scale-balanced">
    Apply the same Command across multiple Objects to compare cleanly.
  </Card>

  <Card title="Sector and competitive analysis" icon="diagram-project">
    Use Protocol-level Commands to map competitive landscapes.
  </Card>

  <Card title="Sourcing for reports" icon="file-lines">
    Pull consistent data structures across many entities for written research.
  </Card>
</CardGroup>

## A structured approach to deep dives

Research benefits from a consistent sequence. The Object + Command model is designed for this — once you learn a Command on one Object, the same Command applied to another Object behaves identically.

### Token deep dives

A typical sequence for evaluating a single token:

<Steps>
  <Step title="Orientation">
    **Token Description (TKD) ↗** — high-level summary, key attributes, market position.
  </Step>

  <Step title="Supply structure">
    **Tokenomics (TKE) ↗** — total supply, circulating supply, emission schedule, vesting.
  </Step>

  <Step title="Holder analysis">
    **Ownership (OWN) ↗** — concentration metrics, large-holder activity, distribution.
  </Step>

  <Step title="Cross-chain presence">
    **Multichain Monitor (MTM) ↗** — activity and supply across chains, if applicable.
  </Step>

  <Step title="Funding and history">
    **Fundraising (FRS) ↗** — funding rounds, investors, historical raises.
  </Step>

  <Step title="Activity and liquidity">
    **Live Trades (LTD) ↗** and **Market Liquidity Analysis (MLA) ↗** — current trading behavior and depth.
  </Step>
</Steps>

The full sequence is documented in [Token due diligence](/docs/guides/by-workflow/token-due-diligence).

### Protocol deep dives

For protocols, the sequence starts with **Protocol Analysis (PRA) ↗** for fundamentals, moves to **User Acquisition (UAC) ↗** and **User Profile (UPO) ↗** for growth and demographics, then to **Competition (PCP) ↗** for the competitive landscape. For protocols with DEX activity, **DEX Performance (DEP) ↗** and **DEX User Analysis (DUA) ↗** add venue-level depth.

## Comparative analysis

When evaluating two or more Objects against one another:

* Use the **Token Comparison (TCP) ↗** Command for direct side-by-side token analysis.
* For protocols, apply the same Command (e.g. `PRA`) to each Object in turn, comparing the same metrics across each view.
* Use watchlists to group the Objects under comparison so you can return to them quickly.

## Sourcing data for reports

When pulling figures or charts for written research:

* Set your **currency** and **timezone** before sourcing data so that every figure is consistent.
* Note the **methodology references** included in each Command — these are typically linked from info notes near the relevant data.
* For programmatic access, see the [Data API](/docs/data-api/introduction) for the same datasets used by the terminal.

## Commands frequently used by analysts

| Command | Purpose            |
| ------- | ------------------ |
| `TKD`   | Token Description  |
| `TKE`   | Tokenomics         |
| `OWN`   | Ownership          |
| `MTM`   | Multichain Monitor |
| `FRS`   | Fundraising        |
| `TCP`   | Token Comparison   |
| `PRA`   | Protocol Analysis  |
| `PCP`   | Competition        |
| `UAC`   | User Acquisition   |
| `UPO`   | User Profile       |

The full catalog is available in the [Command Reference](/docs/core-concepts/commands/command-reference).

## Related workflows

<CardGroup cols={2}>
  <Card title="Token Due Diligence" icon="clipboard-check" href="/docs/guides/by-workflow/token-due-diligence">
    A complete sequence for evaluating a token.
  </Card>

  <Card title="Tracking Smart Money" icon="wallet" href="/docs/guides/by-workflow/tracking-smart-money">
    Surfacing meaningful wallet activity for research.
  </Card>
</CardGroup>