> For the complete documentation index, see [llms.txt](https://devai.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devai.gitbook.io/whitepaper/why-devai/low-fees.md).

# Low Fees

DEVAI takes pride in offering its users an exceptionally cost-effective solution for deploying smart contracts across various blockchain networks. With our transparent fee structure, users enjoy the convenience of a flat service fee of $90 - $120 based on native token price fluctuation, regardless of the chain they choose to deploy on. This unparalleled affordability ensures that deploying through DEVAI remains accessible to all users, regardless of their budget or the complexity of their project.

| Blockchain          | Service Fee |
| ------------------- | ----------- |
| Solana              | 1 SOL       |
| Ethereum            | 0.05 ETH    |
| Binance Smart Chain | 0.2 BNB     |
| Avalanche           | 2.5 AVAX    |
| Arbitrum            | 0.05 ETH    |
| Polygon             | 100 MATIC   |

{% hint style="warning" %}
Refer to "Know Your Fees" section for a complete breakdown of costs and gas fees to launch a project on each chain.
{% endhint %}


---

# 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://devai.gitbook.io/whitepaper/why-devai/low-fees.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.