Every screen in Peak is the combination of an Object and a Command. Once you understand this pairing, the entire product becomes predictable.
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.
A concrete example
Consider the viewSOL TKD:
SOLis the Object — the Solana token.TKDis the Command — Token Description, a summary view that includes key attributes, supply, market data, and links to related analyses.
SOL TKE— Tokenomics for SolanaSOL OWN— Ownership and holder concentration for SolanaSOL LTD— Live trade stream for Solana
ETH TKD— Token Description for EthereumUniswap PRA— Protocol Analysis for Uniswap
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,TTC) - Trading Statistics — activity, liquidity, and trader behavior (
TDA,PFA,LTD,CWT)
Command naming conventions
Every Command has:- A full name — e.g. Token Description, DEX Performance
- A three-letter abbreviation — e.g.
TKD,DEP
- The header pill when the command is active
- Cross-reference links in content
- The Suggested Commands footer
- Search results
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.
The standard shell
Every Command, whether scoped to an Object or Object-less, renders inside the same shell:
This consistency means once you learn one Command’s layout, you understand the structure of every Command in Peak.
Next steps
Navigating Peak
Learn how to move between Objects and Commands efficiently.
Cross-references & Workflows
Understand how Peak links related views into research workflows.

