Skip to main content

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 exposes two HTTP surfaces:
APIBase URLAuthUse for
Fuse APIhttps://zap.dzap.ioNone (per-IP rate limits)Intent execution, bundles, gasless
Trade APIhttps://api.dzap.ioOptional API keySwaps, bridges, DCA, tokens, status
Both speak JSON over HTTPS. Both run on the same routing engine.

Pick one

Fuse API

OpenAPI-backed. Quote, build, bundle, execute, status.

Trade API

REST routes for the full Core surface plus DCA and webhooks.

Conventions

  • Amounts are strings in wei"1000000" is 1 USDC (6 decimals), not 1.
  • Native tokens use the sentinel 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE. Never the zero address.
  • Slippage is percent1 = 1%, 0.5 = 0.5%.
  • Errors follow { "status": "error", "code": "...", "message": "..." }. See Error Codes.

Status & rate limits

AspectFuse APITrade API
Health endpointGET /v1/statusGET /v1/status
Default rate limit3 req/sec on quote/buildTxPer-key (or per-IP fallback)
AuthNoneBearer-style API key (optional)
Response time SLATypical: <200ms quote, <500ms buildTypical: <300ms quote
See Authentication and Rate Limits.

Versioning

All endpoints are under /v1. Breaking changes ship under /v2; /v1 stays available with at least 90 days notice. Watch the changelog.