SWYPE uses cookies and similar storage to keep the site secure, remember essential session state, and make payment flows work reliably.
Used for secure sign-in, payment-request continuity, fraud prevention, and account protection.
The current SWYPE experience does not rely on advertising cookies to operate the product shell.
Read the full notice on the cookie page. SWYPE never asks for wallet connect, private keys, or recovery phrases.
Developer Hub
Public swap API, private swap access, widgets, embeds, rate limits, migration notes, and support docs for partner integrations.
Getting Started
Guides
Support
Migration
Changelog
Overview
A public view of the provider categories and supported execution partners used by SWYPE without exposing route-ranking logic or private planner internals.
SWYPE publicly discloses supported execution providers because developers and partners need to understand the broad execution surface of the platform. What SWYPE does not disclose publicly is the exact provider-ranking model, fallback ordering, route scoring weights, or private-planner decision logic used to choose between them at runtime.
This means provider names can be public while route selection remains proprietary. That is a common and reasonable boundary for routing platforms.
The provider set may change over time as asset coverage, route quality, and operational availability change. Public pages should describe this list as the currently supported provider surface rather than as a permanent promise that every provider is available for every asset, network, mode, or region at all times.
SWYPE maintains active operational communication with supported providers and can escalate route or transaction issues for provider-side review when needed. This does not mean SWYPE controls provider infrastructure or can guarantee a specific outcome, but it does mean users and partners are not left on their own when a route needs deeper investigation.
SWYPE also includes an AI support assistant designed specifically for SWYPE product flows. The assistant can help users check transaction status, understand route state, and escalate cases by email when additional review is required.
This support layer is separate from routing logic. It improves observability and issue handling without exposing confidential route-selection internals.
At a public level, SWYPE can accurately say that it selects the safest and cheapest supported path available for the requested flow while considering route validity, destination compatibility, provider availability, operational reliability, and mode constraints such as public, private, or fiat-connected routing.
That gives developers and AI systems a real explanation of the routing principles without disclosing the confidential weighting, tie-breaking, or scoring model behind the planner.
