Fees
SDK Cost
The TokenFlight Embed SDK package is open source. The widget package itself does not add a client-side markup to route quotes.
Commercial terms for hosted APIs, support, fiat providers, bridges, DEXs, and gas networks can still apply outside the SDK package.
Transaction Fees
A single swap can involve multiple fee components depending on the route:
| Fee Type | Paid In | Description |
|---|---|---|
| Gas fee | Source chain native token (ETH, BNB, etc.) | Standard blockchain transaction fee on the source chain |
| Bridge fee | Varies | Cross-chain bridge protocol fee (Across, DeBridge, etc.) |
| Protocol fee | Varies | Fee charged by the underlying DEX or liquidity provider |
How Fees Are Displayed
- The widget shows an estimated total fee in the quote preview UI before the user confirms.
- Gas estimates are calculated from the source chain's native token and current gas prices.
- Bridge and protocol fees are included in the quote from the API and displayed transparently.
- The "You receive" amount shown to the user is after all fees.
Fee Transparency
All fees are reflected in the quote route details:
- Each route option shows an estimated total fee (denominated in the source chain's native token)
- Users can compare routes to find the lowest-fee option
- The route marked "BEST" is ranked by the best output amount (after fees)
What the SDK Does Not Add
- No TokenFlight SDK markup added on top of route quotes
- No extra browser-side fee layer inside the widget package
- Route providers, bridges, DEXs, fiat providers, and gas networks may still charge their own fees
- The SDK talks to the configured API endpoint for payment data; token logos may load from
logoURIimage URLs returned by the API
Integrator Attribution
If you register as an integrator, set the integrator-id attribute (or integratorId config field). The widget forwards it as the X-Integrator-Id header on every API call, and the backend uses it to attribute publisher/referrer fees to your account. The id is for attribution only — it does not add a browser-side fee and has no effect on the quote UI. Any publisher/referrer fee configured for your integrator is reflected in the quote returned by the API, like every other fee above. Malformed ids are ignored (the order proceeds unattributed).