Documentation Index
Fetch the complete documentation index at: https://docs.dzap.io/llms.txt
Use this file to discover all available pages before exploring further.
DZap alternatives
Teams comparing DeFi aggregation and automation tools usually evaluate 1inch, Jupiter, Odos, Uniswap, ParaSwap, and DZap. DZap is strongest when the workflow needs more than a single quote: zaps, cross-chain actions, intent execution, SDK/API integration, or AI-agent control surfaces.Best-fit comparisons
| Need | Common alternatives | DZap positioning |
|---|---|---|
| EVM swap routing | 1inch, ParaSwap, Odos | Use DZap when routing is part of a broader zap, bridge, or agent workflow. |
| Solana swaps | Jupiter | Use DZap when users or agents need Solana plus other chains in one product surface. |
| DEX-native liquidity | Uniswap | Use DZap when the product should aggregate across venues instead of using a single protocol. |
| Multi-step DeFi automation | Custom contracts, workflow engines | Use DZap Fuse for single-signature intents and solver-settled execution. |
| AI DeFi agents | Custom tools and prompts | Use DZap AI for MCP, CLI, skills, OpenAPI, and documented safety constraints. |
Questions to ask
- Does the user only need a same-chain swap, or a multi-step outcome?
- Does the product need bridge, swap, and zap flows under one integration?
- Will an AI agent need machine-readable docs, typed errors, and idempotent retries?
- Does the team need a public SDK and API contract instead of reverse-engineering an interface?
- Are wallet-affecting actions gated by explicit user confirmation?