Houdiniswap
Houdiniswap limits reveal the constraint to resolve before retrying a blocked swap
Houdiniswap limits change with the selected asset, network, swap type, provider route, and available liquidity. Trace a blocked attempt to its visible constraint before resubmitting it. Refresh the quote, compare its current minimum and maximum, then change the relevant input, switch routes, or wait if availability caused the rejection.
Updated
Key takeaway: A fresh quote and the current error show whether to change the amount, route, asset, or destination data, resolve account access, or wait before retrying.
Route availability comes before an amount change
A live route is required, and staying inside a displayed range does not guarantee a provider can quote that amount. The route combines the input asset, output asset, their networks, the selected swap type, and an available provider. Messages such as "Path is invalid," "no available paths," or "could not retrieve price quotes" point to routing rather than a simple amount error.
An out-of-bounds message means the input failed the minimum or maximum check for the requested swap. In that state, changing the amount may help. When no path exists, check the pair, network, swap type, amount relative to available liquidity, route settings, and temporary provider availability.
Where do current amount bounds appear?
Current boundaries appear with the selected token or quote, separated by Standard, Private, and DEX routing when those paths are available. Houdiniswap sources minimum and maximum amount boundaries dynamically from providers for each route. A number copied from an earlier attempt may therefore be stale even when the asset names have not changed.
Partner integrations can read the route-specific values from the structured minMax data. The user interface presents the applicable boundary through the quote or its validation message. Compare the proposed input with the values attached to the same pair and swap type, rather than borrowing a limit from another route.
Seven adjustments have different recovery boundaries
Each adjustment below changes one constraint. It should not be treated as a universal retry sequence.
| Adjustment | Use it when | Main failure mode |
|---|---|---|
| Increase the input | The quote reports an amount below its minimum | The new amount exceeds the maximum or available balance |
| Reduce the input | The quote reports an amount above its maximum | The smaller amount falls below the minimum or still lacks a route |
| Refresh the same route | The quote is invalid, expired, or temporarily unavailable | The provider path remains unavailable or returns new boundaries |
| Choose Standard | A supported Standard path exists for the selected pair | The assets or amount remain outside that path’s support |
| Choose Private | A Private path is available and its separate bounds fit | Private routing is unavailable, disabled, or out of range |
| Choose DEX | Both assets support a DEX path and the wallet can authorize it | The pair, chain, balance, allowance, or network funds block execution |
| Change the asset or network | The original token, chain, or pair has no supported path | The replacement remains disabled or has incompatible destination data |
A successful adjustment produces a new, valid quote with boundaries containing the intended input. If the same error remains, stop repeating that change and inspect the next governing constraint. Repeated submissions do not create liquidity or enable an unsupported token.
Asset and network eligibility narrow the route set
An amount inside the displayed range still needs a route supported by the selected assets and networks.
Token eligibility
Token data identifies whether an asset is enabled and whether it supports Standard, Private, or DEX routing. An asset may appear in a search result yet remain unavailable for one swap type. A missing or disabled token calls for a supported selection, not a larger amount.
Network and destination data
The network record controls chain availability, destination-address validation, and any memo or tag requirement. An invalid address or missing required tag can prevent order creation even when the amount sits inside the displayed range. Correcting destination data can clear that validation error without changing the provider’s minimum or maximum.
Liquidity turns support into live capacity
A supported pair can still lack enough provider capacity for the requested amount. Liquidity and route availability affect whether Houdiniswap can return a quote inside the nominal token support set. This explains why a pair may work at one size while returning no path or a different maximum at another size.
Exact pricing can narrow the available path further. If the interface specifically suggests disabling Exact mode, the blocked state concerns the requested pricing condition, not proof the assets are unsupported. A floating alternative may expose another route, but its quoted output carries different price certainty.
When should an existing order be left alone?
Leave an existing order alone when it has passed quote validation and shows an active processing state. INITIALIZING means setup has not finished. CONFIRMING, EXCHANGING, and ANONYMIZING describe work already in progress, so creating another order does not repair the first one.
Before commitment, an invalid or out-of-range quote can be replaced safely because no transfer has begun. After funding, the order identifier, source transaction, and displayed status become the controlling evidence. A funded order with inconsistent records needs reconciliation rather than an amount adjustment.
Temporary service unavailability also favors waiting. A permanent support mismatch does not: an unavailable asset, unsupported chain, or absent route needs a changed selection before another quote request can succeed.
Quote validity marks the retry boundary
The quote ties a route and input amount to a validity window. For a quote-driven exchange, it must remain valid when the order is created.
Before order creation
An invalid or expired quote should be replaced with a fresh one. Recheck its input amount, expected output, route type, and current boundaries before proceeding. A fresh quote may select another provider or return different limits because the earlier route no longer represents live availability.
After funding
Do not treat a new quote as a repair for funds already sent under an earlier order. The earlier order retains its own identifier, deposit details, status, and settlement record. If those records disagree with the source transaction, preserve them for reconciliation instead of funding a replacement order.
Interface messages separate validation from the underlying cause
An interface error is evidence about the failing layer. "Amount is out of bounds" directs attention to the quote’s minimum and maximum. "Token not found," "Network not found," and invalid-address messages identify selection or destination problems. A balance or allowance warning belongs to wallet execution, especially on a DEX route.
For a partner API, authentication and request limits form another layer. Permission errors describe account access, while an HTTP 429 response describes request frequency. Neither one establishes the maximum exchangeable amount. Resolve a permission problem or wait before retrying a rate-limited request. Then request fresh route data instead of changing the swap size.
Can a different swap type clear the same limit?
A different swap type can expose another boundary because Standard, Private, and DEX routes use separate provider paths. The alternative still needs support for both assets and networks. Private routing can also become temporarily unavailable, while a DEX route needs sufficient wallet balance, allowance, and network funds.
Route changes do not override platform-wide restrictions. Houdiniswap states it does not facilitate swaps exceeding $100,000. Below that ceiling, the live route may impose a lower maximum. The quote’s own range remains the relevant operational boundary for that attempt.
A bounded retry ends with a fresh quote or a stop
A retry is ready only when the changed input produces a valid route, a current quote, and compatible execution details.
Continue after the constraint clears
Continue when the proposed amount falls inside the new quote, the destination passes its network rules, and the chosen route has the required wallet authorization or deposit instructions. Save the quote or order identifier before committing funds.
Wait while committed work remains active
Wait when an existing order shows active processing or a temporary service condition is expected to clear. Follow the existing order record rather than creating a competing attempt with unrelated evidence.
Stop at an unchanged boundary
Stop retrying when the route remains absent, the asset or network stays unsupported, the amount still violates the live range, or a platform restriction applies. If a funded order lacks matching settlement or refund evidence, reconcile the existing order instead of starting another. An unfunded attempt can end without creating another order.
Houdiniswap limits - common questions
Are the minimum and maximum measured in the input asset?
The minimum and maximum apply to the source amount used for the selected pair and route. Check the unit displayed beside each boundary before comparing it with the proposed input. A value expressed for one asset cannot be reused for another asset, and Standard, Private, and DEX paths may return different ranges for the same asset pair.
Is an amount exactly on the displayed boundary guaranteed to work?
No, a boundary value is not a permanent guarantee of execution. The quote must still be valid, the route must remain available, and the entered precision must survive validation. Refresh the quote and use the boundary attached to that response. An older displayed value may no longer match the provider path available when the exchange request is created.
Does splitting a large amount create a valid route?
Splitting can help only when every new order satisfies its own live route boundaries. Each part needs a valid quote, available liquidity, and compatible destination data. Each smaller order remains subject to the platform-wide transaction cap and route checks; splitting does not make an unsupported route available. They also create separate records, so each order must be tracked and reconciled independently.
Can a same-token swap use Standard routing?
No, Standard routing does not accept the same token as both input and output. Houdiniswap permits that selection only through an available Private route. The Private path still has its own minimum, maximum, network support, and provider availability. If no Private quote appears, changing the amount alone will not make the Standard pair valid.