For Research Analysts

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

​

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: The full sequence is documented in 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 for the same datasets used by the terminal.

​

Commands frequently used by analysts

The full catalog is available in the Command Reference.

​

Related workflows