> For the complete documentation index, see [llms.txt](https://docs.thevolumeterminal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thevolumeterminal.com/getting-started/readme.md). # What is the Volume Terminal? The Volume Terminal is an institutional-grade trading rewards platform that aligns the incentives of projects, exchanges, and traders. In traditional financial markets, market makers and high-volume traders negotiate private rebate deals with exchanges. In Web3, token projects and exchanges launch public liquidity incentives. Volume Terminal democratizes this process, providing a unified dashboard where any trader can connect their exchange account, participate in active campaigns, and earn a share of reward pools. ``` ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │ Connect CEX API │ ──> │ Trade & Compete │ ──> │ Earn On-Chain │ │ (Read/Trade) │ │ On Active Pairs │ │ Token Rewards │ └─────────────────┘ └─────────────────┘ └─────────────────┘ ``` *** ### Developed by Miren Partners Volume Terminal is built and powered by [Miren Partners](https://www.mirenpartners.com/), a premier Web3 growth consultancy firm specializing in volume generation and market execution. Rather than functioning as a traditional marketing agency, Miren Partners acts as a growth execution layer that transforms incentives, campaigns, and partner distribution into consistent, fee-paying trading volume. By connecting projects to a global network of over 100+ professional trading communities across the APAC, MENA, US, and EU regions, Miren Partners facilitates deep liquidity and sustainable trading activity. Notably, between January 1, 2026 and the end of April 2026, the platform successfully processed over $556M in total trading volume and 167.3K trades, distributing more than $20K in rewards directly to traders' Web3 wallets. *** ### The Problem with Traditional Trading Rewards Existing trading rewards and airdrop campaigns are often opaque, prone to sybil manipulation, and difficult to track: * **Opaque Rules**: Traders rarely know where they stand on leaderboards in real time. * **Complex Integrations**: Interacting with multiple decentralized and centralized exchanges requires navigating a maze of different dashboards. * **Vulnerability to Bad Actors**: Wash-trading bots and sybil attackers dilute rewards for real, organic traders. ### The Volume Terminal Solution Volume Terminal solves these issues by providing a transparent, secure, and data-driven infrastructure: * **Unified Dashboard**: Monitor your volume, open positions, trading history, and current campaign rankings across multiple exchanges from a single interface. * **Real-Time Analytics**: View updated leaderboards, volume progress, multiplier schedules, and time-to-epoch limits on the fly. * **Sybil & Wash Trading Protection**: Proprietary backend monitoring ensures rewards are distributed to legitimate market participants, filtering out toxic wash-volume. * **Direct On-Chain Payouts**: Rewards are computed by the platform and settled directly to your self-custodial Web3 wallet, eliminating counterparty risk. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.thevolumeterminal.com/getting-started/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.