> 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/overview.md).

# Overview

Introduces GetPaid, a proposed multi-chain fee-routing layer for launchpads, its configurable destinations, scope, and pre-testnet status.

GetPaid is a proposed fee-routing layer for launchpads. It is designed to sit between a launchpad's trading-fee flow and its chosen destinations.

```
Launchpad
    ↓
Trading fee
    ↓
GetPaid fee layer
    ↓
Creator / Burn / Buyback / Protocol
```

GetPaid is infrastructure, not a launchpad. It does not issue launches, replace launchpads, or act as a bridge. Its role is to provide a configurable layer through which an integrated launchpad could route fees.

The proposed design brings together:

* Multi-chain fee routing
* Multi-rail settlement
* Creator payouts
* Holder and community participation
* Protocol treasury flows

{% hint style="warning" %}
**Status as of September 27, 2026:** GetPaid is a Version 0.1 pre-testnet concept. It has not been deployed, audited, or launched.
{% endhint %}

The architecture described in these docs is proposed. It remains subject to design, testing, and review.


---

# 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/overview.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.