> For the complete documentation index, see [llms.txt](https://fincake.gitbook.io/fincake-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fincake.gitbook.io/fincake-whitepaper/mechanics.md). # Mechanics Fincake is a tracker for all assets. Through APIs and coordinated parsing, we collect information from multiple projects and blockchains. The system allows to visualize, analyze, execute and aggregate transactions on Bitcoin, Etherium, Solana, BSC, Cardano, Polkadot, Terra, Avalanche, Near, Tron, Cosmos, Polygon, Everscale etc blockchain networks. The service allows you to track NFT, tokens associated with wallets, revenue farms, LP positions, margin positions and more. Users can participate in various DeFi project activities (farming/liquidity provisioning). You can also add traditional investment assets to your portfolio: stocks, bonds, ETFs, etc. The information is summarized in convenient tables and charts. The most important advantage of Fincake is the social component. In particular, the tokenomics of the project is designed to stimulate activity within the platform. --- # 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://fincake.gitbook.io/fincake-whitepaper/mechanics.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.