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

# Partner Attribution

The Partner Attribution Program allows third-party integrators to build on top of Lighter and offer its trading infrastructure through their own frontend. Integrators can configure trading fees for users accessing Lighter through their interface, within global limits set by Lighter.

#### Integrator Fees

Integrators may configure fees for both spot and perpetual markets.

Global limits set by Lighter:

* Perpetual markets: up to 10 bps, or 0.1%
* Spot markets: up to 100bps, or 1%
* Minimum fee increment: 0.01 bps

#### Requirements

Trades containing partner attribution attributes with non-zero integrator fees will require the client submitting them to be on a Plus or Premium/Advanced [account type](https://docs.lighter.xyz/developers/reference/account-types). To check the account type of a client, you can use the [accountLimits](https://docs.lighter.xyz/api/account) endpoint. To change account type, use [changeAccountTier](https://docs.lighter.xyz/api/account), or click on your account type in the [Portfolio](https://app.lighter.xyz/portfolio) page. Zero-fee attribution (tracking only) works on any account type, including Standard.

#### User Approval

Before fees can be applied, the user must sign a message approving the integrator’s fee configuration.

This approval:

* authorizes the integrator to charge the configured fees
* includes an expiry period (if integrator decides to include one)
* can be revoked by the user at any time

The approval's signature requirements depend on whether the integrator and user share the same L1 account, and on whether fees are non-zero.

* Different L1 accounts, non-zero fees: L1 approval + L2 confirmation
* Same L1 account, or zero fees: L2 confirmation only

#### Begin your Integration:

API Docs: <https://docs.lighter.xyz/developers/integration-guides/partner-attribution>

Python SDK: <https://pypi.org/project/lighter-sdk/>


---

# 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.lighter.xyz/programs/partner-attribution.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.