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

# Developer Incentives

### **Overview**

Developers are the backbone of 402Gate’s expansion.\
Every verified API or endpoint integrated with the protocol automatically earns a share of the protocol’s revenue.

#### **Reward Types**

1. **Integration Rewards**\
   Developers who deploy verified 402Gate endpoints receive up to **3–5%** of all transactions routed through their endpoints.
2. **Adoption Bonuses**\
   Additional $402G tokens are granted based on active user count, transaction volume, or sustained uptime.
3. **SDK & Plugin Contributions**\
   Open-source contributors who improve the SDK, templates, or Web2 plugins (WordPress, Shopify, Express) receive bounties from the **Developer Fund**.

#### **Payout Mechanism**

All developer rewards are distributed **automatically on-chain**, recorded transparently, and viewable in the analytics dashboard.


---

# 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/developer-incentives.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.