> For the complete documentation index, see [llms.txt](https://docs.402gate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.402gate.com/ecosystem-and-rewards/partner-and-provider-revenue-sharing.md).

# Partner & Provider Revenue Sharing

### **Overview**

Enterprises, API platforms, and data providers can join 402Gate as **partners**, integrating pay-per-use monetization into their infrastructure while earning passive income.

#### **Revenue Flow**

1. Partner defines endpoint pricing and wallet address.
2. 402Gate routes verified payments through their channel.
3. Partner receives **85–95%** of transaction value directly.
4. Remaining **5–15%** is split among protocol treasury, buyback fund, and developer incentives.

#### **Benefits**

* 💸 **Automatic Revenue Split**  No manual accounting or settlements.
* ⚙️ **On-Chain Transparency**  All payouts verifiable on Solana.
* 🌐 **Plug & Earn**  Integrate once, earn indefinitely from API usage.


---

# 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://docs.402gate.com/ecosystem-and-rewards/partner-and-provider-revenue-sharing.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.