SDK Advantages
Rubic has developed a qualitatively new feature-integration capability for partners and users. Exchange 15,000+ tokens in your dApp, Wallet, or Platform with Cross-Chain Routing and On-Chain swaps.
The Rubic SDK offers On-Chain and Cross-Chain swaps at the best-possible rates. 50% of Rubic commission goes to partners. Integration is free!
Our SDK is built on the basis of Rubic Cross-Chain protocol frontend part. Rubic SDK is a library for interacting with more than 60 DEX's, as well as Rubic Cross-Chain swaps.
- 1.The ability to integrate Rubic's solutions according to the individual requirements of the partner
- 2.Full Customization
- 3.The Rubic SDK offers On-Chain and Cross-Chain swaps at the best-possible rates on any platform
- 4.Completely Free Integration
- 5.The opportunity to receive up to 50% of the income from Rubic’s fees
All of the 21 networks are supported in our SDK.
- 1.It can be used in any JavaScript-compatible application.
- 2.Unlike the Widget, the SDK allows you to integrate the functionality of Rubic without being tied to a specific user interface. You can quickly integrate the SDK into your dApp, Wallet, or Platform without tediously needing to working with various DEXs (Uniswap, 1inch, SushiSwap, etc.) and blockchains. You no longer need to think about which blockchain to integrate, as Rubic integrates all the most popular & up-and-coming blockchains.
- 3.The SDK can be used in any frontend application, regardless of the framework used (react, Angular, Vue, etc.), or in a JavaScript application that does not use the framework at all. You can also use the SDK to calculate the trade on the NodeJS server; however, it will be impossible to conduct a transaction on the server on behalf of the user. In the future, we’re planning to develop a module for a more complete SDK integration on the server, as well as specialized modules for specific frontend frameworks for even faster SDK integrations.
We will regularly update the npm package, while backward compatibility will not be violated. However, over time, backward-compatible versions may appear; with global improvements and new functionality. In this case, we recommend all integrators to update their code, but it will be possible to stay on the old version as its performance will not be disrupted.
Last modified 4mo ago