Skip to main content
DZap is a DeFi aggregation protocol. Instead of integrating DEXs and bridges one by one, you integrate DZap and route across all of them. Surfaces: Core (swap + bridge aggregator), Fuse (single-click intent execution), and the Widget (embeddable React UI).
Not to start. The Fuse API (zap.dzap.io) is public and rate-limited per-IP. The Trade API (api.dzap.io) accepts optional API keys for higher rate limits and per-route configuration. See Authentication.
Core is route-and-execute, you ask for a quote, sign a transaction, send it. Fuse is intent-based, you sign an intent describing the outcome you want, and a solver settles it (gasless variants supported via EIP-712 permit). See Product Stack.
Fuse is the public-facing brand for the intent execution layer. Code, repos, and SDK methods still use Zap* names, the rename is gradual. When you see getZapQuote, signGaslessDzapUserIntent, etc. in the SDK, that’s Fuse.
Most major EVM chains plus Solana and Bitcoin (for bridge endpoints). The full live list comes from getAllSupportedChains() in the SDK and the /v1/config/chains endpoint. See Supported Chains.
Yes. @dzapio/widget is a React SDK for swap, bridge, and zap UI. @dzapio/wallet is the multi-chain wallet layer it uses (EVM, Solana, Bitcoin, Sui). See Widget.
Open an issue on the relevant repo or ping us in Discord. For security issues, email support@dzap.io directly, see Security.
Last modified on October 15, 2026