deBridge

debridge.finance ↗

Token delivery across chains with developer controls

SI Score
80/100
Pricing
Pay-As-You-Go AI reading, not confirmed
Free plan
No AI reading, not confirmed
Sign-up required
Not required AI reading, not confirmed

Ask SI about deBridge

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the deBridge homepage

What it does

deBridge arranges token exchanges within and between blockchains. Its liquidity network, embedded widget and API connection let applications request a destination asset and track the resulting order.

A deBridge cross-chain order specifies the result the user wants, such as receiving USDC on Base after spending SOL on Solana. The input enters a contract on the starting chain, and a solver supplies the requested tokens to the recipient on the destination chain. Each order has its own funds rather than contributing to a shared trading pool. Applications can also arrange same-chain swaps and attach follow-on contract calls.

The developer API supports public access without a key at 50 requests per minute. Commercial integrations must obtain a dedicated key; authenticated access is documented at 300 requests per minute. That distinction makes the public interface useful for evaluating the integration, while production access needs its own registration step.

For order creation, the create-tx endpoint returns an estimate and a transaction together. Without the required recipient and authority addresses it returns only the estimate, allowing a preview before a wallet connects. Once those addresses are known, request the full pair. Do not copy the quoted input and output amounts into a second request: fixing both can turn it into a limit order which solvers may leave unfilled. If roughly 30 seconds pass, obtain a fresh quote and transaction.

Costs include a chain dependent flat protocol charge and a 0.04% protocol charge on the input amount, plus solver margin, operating expenses and any other applicable route costs. The response breaks down the estimates. Use those live values rather than putting a fixed fee into an application, especially when an approval or a swap on either chain adds costs.

Cancellation is available for an unfulfilled order and must be initiated on the destination chain by its designated order authority. The refund beneficiary is the source chain authority set when creating the order. Cancellation can return protocol and affiliate charges along with the input, but it also needs network and messaging payments. An integration should preserve those authority addresses and explain the cancellation cost before someone funds an order.

Strengths

  • Supports same-chain swaps and destination-chain token delivery
  • Returns the estimate and signing transaction as one coordinated response

Watch out for

  • Commercial API integrations require a dedicated key
  • Stale or unattractive orders can remain unfilled
  • Cancelling an order involves further network and messaging costs

Best for

  • Developers adding destination-chain token delivery
  • Applications that need explicit order authority and cancellation handling

Sources