# Fees

## Fee Structure

At Protocolink, our primary aim is to offer a streamlined, cost-efficient environment for our users. Our fee structure is transparent and designed to cater to various transaction types. Here's a comprehensive breakdown:

**Flashloan Fees**:

* Utilizing flash loans attracts a fee determined by the service provider. Protocolink adds an additional fee of 0.05% for the facilitation of these services.
* Aggregator Utilization: Protocolink employs our flashloan aggregators to guarantee that the selected service provider offers both the lowest cost and ample liquidity.

**Initial Fund Deployment or Borrowing Fees**:

Every initial fund deployment or borrowing process through Protocolink incurs a fixed fee of 0.2%, covering the infrastructure and ensuring secure and prompt transactions.

**Payment Modality:**

Fees are collected in the native token of the network on which the transaction occurs. As an example, transactions executed on the Polygon network will levy fees in MATIC, while those on the Ethereum network will incur charges in ETH.

## Fee Sharing for Developers

We value the immense contributions of developers. Hence, fees generated by Protocolink can be shared with developers who initiate transactions. We will maintain a 50:50 sharing ratio, promoting a mutually beneficial ecosystem.

**Fee Sharing Process:**

* **Participation**: Developers can seamlessly partake in our fee-sharing program without undergoing complex application processes.
* **Eligibility**: Developers become eligible by initiating transactions via Protocolink's API. The fees generated from these transactions are subject to sharing.
* **Distribution**: With a fair 50:50 sharing ratio, and post-transaction verification, profit-sharing is automated. This ensures that developers receive their rightful share without delays.
* **Tracking**: Developers can employ Dune Analytics to track their fee-sharing numbers, allowing for transparency and up-to-date information.

If you wish to include a referral for fee sharing, you can append the `referral` property to the `routerData` object. For detailed information on using `routerData`, please refer to the [Router Data Documentation](/protocolink-sdk/api-sdk-interfaces/global-types.md#routerdata).

{% hint style="info" %}
Dune Analytics dashboard is under development, stay tuned!
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.protocolink.com/fees.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.