> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/conclusion/why-getpaid.md). # Why GetPaid Explains why GetPaid proposes a generalized fee-routing layer for launchpad ecosystems across chains, payout rails, and recipient groups. Trading fees already exist across launchpads and token ecosystems. Their routing can still be constrained by chain, payout rail, recipient structure, token utility, and creator flexibility. GetPaid proposes a generalized infrastructure layer for that routing. It is designed to direct fees across multiple chains and payout rails, with configurable allocations for creators, holders, a protocol or community treasury, and proposed burn and buyback mechanisms. GetPaid is not trying to replace launchpads. It is designed to sit alongside existing launchpad infrastructure as a Fee Layer that receives and distributes eligible fees under defined rules. > GetPaid is not the first. GetPaid is a generalization. The proposal builds on patterns already demonstrated in creator fee routing, holder rewards, launchpad fee models, multi-platform creator systems, and stock-token ecosystems. Its distinction is the proposed combination of those patterns in one infrastructure layer. That thesis remains preliminary. GetPaid is a concept-stage, pre-testnet project. It has not deployed contracts, launched $GET, completed an audit, or established production traction, revenue, or integrations. The model must be validated through implementation, testnet work, security review, integrations, creator adoption, real fee flow, and economic testing. Those results, not the design alone, determine whether the infrastructure becomes useful. --- # 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://whitepaper.getpaid.family/conclusion/why-getpaid.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.