> 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/introduction/the-idea.md).

# The Idea

Explains how GetPaid generalizes existing fee-routing patterns into proposed infrastructure for multi-chain, multi-rail, and multi-recipient launchpad distributions.

> **GetPaid is not a first mover. It generalizes existing fee-routing patterns.**

The thesis is not that fee routing is new. Existing products already demonstrate parts of the model: creator fee routing, holder rewards, multi-platform distribution, AI-driven token launches, and stock-token pairing.

Relevant examples include:

* **UsePaid** for fee routing
* **pump.fun** for pro rata holder rewards
* **Wired Up** for a multi-platform concept spanning X, Instagram, TikTok, GitHub, and Fomo beta
* **bankr** for AI agent launches
* **long.xyz** for stock-token pairing

Pons is another relevant example of a launchpad fee model. These projects are predecessor references only. They are not GetPaid partners, affiliates, or endorsements.

### From product pattern to infrastructure layer

An individual fee-routing product can connect one ecosystem, one chain, or one payout model. GetPaid proposes a generalized layer that could give launchpads a shared routing surface across several dimensions:

| Dimension        | Proposed scope                                          |
| ---------------- | ------------------------------------------------------- |
| Chains           | Multiple chains through chain-specific integrations     |
| Settlement       | Multiple payout rails                                   |
| Recipients       | Creators, holders, and protocol or community treasuries |
| Token mechanisms | Burn, buyback, staking, and governance paths            |

The distinction is architectural. Rather than defining a single fee destination, GetPaid proposes configurable routing between an integrated launchpad and its recipients or token mechanisms.

This is a design thesis, not evidence of adoption or product-market fit. GetPaid remains a pre-testnet concept. Its proposed scope has not been deployed or production-validated.


---

# 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/introduction/the-idea.md?ask=<question>&goal=<endgoal>
```

`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.