> For the complete documentation index, see [llms.txt](https://monoprotocol.gitbook.io/monoprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monoprotocol.gitbook.io/monoprotocol/architecture/monetization.md). # Monetization From inception, applications can define flexible user fees per transaction, configurable by chain and transaction type. Fees collected from users are intended to: * Offset application-subsidized gas fees * Generate rmpust and flexible revenue streams Fees are settled with every user transaction as a transfer to the application wallet. **Revenue Streams:** **Protocol Fee Structure:** * **Execution Fees**: Small fee on all cross-chain operations * **MEV Capture**: Value extracted from MEV protection services * **API Usage**: Subscription fees for developer access * **Premium Features**: Enhanced services for enterprise users **Partner Revenue Sharing**: Applications and partners can earn revenue through: * Transaction fee sharing based on volume * Premium feature access fees * White-label implementation licensing * Custom integration and support services --- # 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://monoprotocol.gitbook.io/monoprotocol/architecture/monetization.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.