> For the complete documentation index, see [llms.txt](https://docs.getrekt.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getrekt.trade/docs/builders.md).

# builders

A third-party interface may help users discover GetRekt, display its data, or prepare transactions. Using another interface does not change on-chain price checks, liquidation rules, claim priority, or the user's wallet-approval boundary.

## Builder attribution is not another fee

Papertrade documents a separate builder-code concept. GetRekt does not currently implement that API or an additional builder rebate. No extra 1% builder fee is included in this book's allocation.

A builder may participate as a referrer only through the same verified referral mechanism available to other eligible referrers. It cannot stack a separate undocumented builder deduction on top of the 2%-then-30/70 cash-loss split. [Referral fees](broken://pages/4ae98f6aa1e3c0a457110b4f9eefb1d3448a99a6).

## Integration requirements

Use the exact published network, package, and object IDs. Show native USDC amounts, margin source, accepted price, executable limits, and queue status accurately. Preserve the signed transaction's sender and destination, and validate resulting on-chain events before showing success.

{% hint style="warning" %}
Do not call a simulated balance a wallet balance, a queued claim withdrawable USDC, or an emitted settlement event proof that every profit was paid. Indexers must distinguish cash transfers, liability changes, referral accrual, and reward minting.
{% endhint %}

The current SDK and deployment checks are described in [Integration](broken://pages/f2e97be1c7dbb94457b8693d9a73abcdc212583d). The new referral and halving events do not yet exist and must not be fabricated by an integration.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getrekt.trade/docs/builders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.