> ## 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. # Objects overview > The Object types in Peak and how they relate to each other. An **Object** is any entity you can analyze in Peak — a token, a protocol, a wallet, a network. Every Command in the product is scoped to one Object type. Understanding the Object model is the foundation for navigating the terminal. ## The Object types Peak organizes the entire crypto market into Object types. Each represents a distinct kind of entity, with its own dedicated Commands. Fungible digital assets. The central Object in Peak — most analytics revolve around token-level data. DeFi applications — DEXs, lending markets, launchpads — analyzed for TVL, users, revenue, and competitive positioning. Centralized trading venues that custody user assets off-chain. Analyzed for reserves, listings, and flow activity. A specific trading pair on a decentralized exchange — the atomic unit of on-chain trading activity. Blockchain addresses controlled by a single entity — individuals, funds, institutions, or smart contracts. Blockchain networks (L1, L2, L3) — the infrastructure layer where tokens, protocols, and transactions exist. Calculated benchmarks representing weighted baskets of tokens. Used for performance tracking and comparison. Curated or algorithmic collections of tokens grouped by narrative themes, industry sectors, or performance tiers. A ninth category — **Cross-Object** — covers Commands that operate across multiple Object types rather than a single one. See [Object-less commands](/docs/core-concepts/commands/object-less-commands). ## How Objects relate to each other Every Object connects to other Objects through typed relationships. These relationships are the foundation of cross-object analytics — they make it possible to ask questions like *"show me all wallets holding tokens from the AI narrative on Solana"*, which traverses three relationships at once. ### The relationship graph ```mermaid theme={null} graph LR Token --> Network Token --> Protocol Token --> DEXMarket[DEX Market] Token --> CEX[Centralized Exchange] Token --> Index Token --> TokenGroups[Token Groups] Token --> Wallet Protocol --> Network Protocol --> DEXMarket Protocol --> Wallet Protocol --> Token CEX --> Token DEXMarket --> Protocol DEXMarket --> Network DEXMarket --> Token Wallet --> Network Wallet --> Protocol Wallet --> CEX Index --> Token TokenGroups --> Token classDef obj fill:#1a1a1a,stroke:#C8A96E,color:#fff,stroke-width:1.5px class Token,Network,Protocol,DEXMarket,CEX,Index,TokenGroups,Wallet obj ``` ### Token Token sits at the center of the graph — most other Objects connect through it. With seven outbound relationships, it is the most connected entity in Peak. * **Deployed on** one or more Networks — a token can exist on multiple chains. * **Used by** Protocols — deposited, traded, or held inside DeFi applications. * **Base of** DEX Markets — one token can be the base asset in many trading pairs. * **Listed on** Centralized Exchanges — tokens trade on multiple CEX venues. * **Constituent of** Indices — included in calculated baskets for performance tracking. * **Belongs to** Token Groups — narrative themes, industry sectors, or performance tiers. * **Held by** Wallets — distributed across many addresses, classified by holder type. ### Protocol Protocols are the application layer of DeFi — DEXs, lending markets, launchpads. They sit between Networks (where they run) and Wallets (who use them). * **Deployed on** Networks — protocols can operate cross-chain. * **Has a native token** — most protocols have one governance or utility token. * **Hosts** DEX Markets — a single DEX protocol contains many trading pairs and liquidity pools. * **Used by** Wallets — every protocol has its base of unique users and depositors. * **Forked from** another Protocol — captures family lineage (e.g. Uniswap V2 forks). ### DEX Market A DEX Market is the atomic unit of on-chain trading — a specific pair on a specific venue. Every DEX Market has exactly one base, one quote, one protocol, and one network. * **Quote token** — each pair has one quote asset (typically USDC, USDT, SOL, ETH). * **Hosted on** a Protocol — every pair belongs to one DEX (Uniswap, Raydium, and similar). * **Lives on** a Network — every liquidity pool exists on exactly one chain. ### Centralized Exchange Centralized Exchanges are the off-chain trading layer — venues that custody user assets and bridge on-chain capital with traditional trading flow. * **Custodies** Tokens — CEXs hold many tokens in reserve wallets, enabling proof-of-reserves verification. ### Wallet Wallets are the actor layer — the entities that hold tokens and interact with protocols. Wallet-to-wallet and wallet-to-CEX relationships capture fund flow. * **Active on** one or more Networks — a wallet (or wallet cluster) can span chains. * **Interacts with** Protocols — every deposit, swap, or borrow creates a wallet-protocol edge. * **Transfers to** other Wallets — peer-to-peer fund movement, the basis of flow analytics. * **Deposits to** Centralized Exchanges — tracks inflow and outflow patterns between on-chain wallets and CEX accounts. ### Index Indices are the simplest Object in the graph — they exist purely to group tokens. * **Contains** Tokens — an index is defined by its constituent token list and weighting methodology. ### Network Networks are the infrastructure layer. They host everything else, but their only outbound relationship is hierarchical. * **Layer of** another Network — L2 and L3 networks sit on top of a parent (Arbitrum on Ethereum, Base on Ethereum, and similar). ### Token Group Like Indices, Token Groups exist to organize tokens — but for narrative or sector slicing rather than performance tracking. * **Contains** Tokens — each group is a curated or algorithmic membership list. ## Next steps Start with the most-used Object type. See the full catalog of Commands organized by Object.