Unified routing and execution for swaps, bridges, and gasless flows through one API.

Universal Market Access for Digital Assets

One integration for chains, assets, routing, and execution.

xPath is Rath's routing and execution layer for onchain asset movement. It connects applications to cross-chain liquidity, DEX routing, bridge providers, token discovery, and gasless execution through one API surface.

Why xPath

Onchain execution is fragmented across:

multiple chains and rollups
bridge providers with different coverage and behavior
DEXs and aggregators per ecosystem
token variants across chains and wrappers
different execution paths for quote, route building, and submission
relayed and gasless flows that need separate handling

Integrating each of these systems independently creates overhead across routing logic, token mapping, transaction building, monitoring, and support workflows.

xPath abstracts that complexity behind a single integration.

What xPath Provides

xPath is the routing and orchestration layer that enables:

same-chain swaps
cross-chain swaps and bridging
route discovery across supported providers
transaction-ready calldata generation
gasless Permit2-based swap execution
token search and supported-chain discovery
route and bridge status monitoring

All through one unified API.

For the request flow, see Introduction.

When to Use xPath

xPath is built for products that need reliable onchain routing and execution:

wallets and embedded wallet platforms
exchanges and trading applications
DeFi frontends and aggregators
fintech apps that need cross-chain asset movement
gasless swap experiences built on Permit2
agent workflows that need route discovery and executable transaction payloads

If your users need to move assets across chains or interact with fragmented liquidity, xPath removes the infrastructure burden.

Without xPath vs. With xPath

	Without xPath	With xPath
Routing	Build custom logic across providers	Use one routing API
Bridge coverage	Integrate and maintain providers yourself	Abstracted behind one surface
Token discovery	Maintain token metadata and search flows	Query unified token endpoints
Execution payloads	Assemble calldata per route manually	Build transaction-ready payloads
Gasless support	Add separate relayer flow	Use dedicated gasless endpoints
Monitoring	Track route and bridge health yourself	Use shared status endpoints
Time to ship	Higher integration and maintenance cost	Faster product integration

Next Steps

Start with the pages that match your integration flow:

Introduction for base URLs, auth, and the core request flow
API Reference for endpoint-by-endpoint details
Quote API to fetch ranked routes
Build Path API to generate executable calldata
Gasless Quote API to start relayed Permit2 execution

xPath Overview