# Dev3 Pricing Plans Dev3 pricing model introduces two plans: * free * prepaid {% hint style="info" %} Prepaid plan only accepts payments in form of native ETH on the Ethereum blockchain network! {% endhint %} ### Free plan The **free plan** is active by default and allows anyone to create the project on the Dev3 Dashboard and start playing around. The only limitation is set upon the number of transaction requests processed by the Dev3 widget. Every project gets **200 transaction requests** for free in order to test the platform and play around. Once the 200 requests threshold has been reached, the prepaid plan is automatically activated.\ This means the workspace owner must buy the transactions by paying in ETH. ### Paid plan Payments are received and processed by our [Dev3 Swapper](https://etherscan.io/address/0x1096998f9531DE5cbF43A772dCa38c17E7F7dFD1#writeContract) smart contract which uses underlying AAPX tokens to unlock paid packages.\ Simply call the `buyTransactions(address wallet)` function and provide your master wallet as a parameter, the one you used for creating a project on Dev3. Send any amount of ETH to this function and Swapper contract will convert ETH to the dollar amount, and then the dollar amount is converted to the number of transactions as defined per [pricing](https://dev3.sh/pricing/).\ \ This way you can buy any number of transactions on demand. As you get close to the limit, simply refill this contract with ETH to buy more transactions. --- # 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.dev3.sh/welcome-to-dev3/pricing/dev3-pricing-plans.md?ask= ``` 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.