BUILT AND RUNNING · ROUTES PROMOTE BY RUNTIME EVIDENCE

One intent.
Every route.
Exact outcome.

Universal Router is an outcome-first execution layer for wallets, payment apps and other products that need to move value across providers and networks without exposing provider, gas or recovery mechanics to the application.

Provider tender, not provider lock-in · runtime capability verification · exact-output constraints · status and recovery as part of execution.
Universal Router
Outcome-oriented execution plan
RUNNING
Intent120.00 USDC → Base
Source mode
AUTO / MULTI_CHAIN
Outcome
EXACT_OUTPUT
Recipient
0x… recipient
Debit constraint
MAX_LOCKED
Discovereligible sources
Tenderprovider candidates
Normalizeall-in outcome
Executelocked plan
Recoverunknown state
Relayeligible
bridge · exact output
Avail Nexuseligible
multi-input · one payout
Across / 0xchecked
intent bridge · swap · gasless profiles
Locked recipient outcome
120.00 USDC · Base
runtime gated ✓
Contract
Outcome-first
Supply
Provider tender
Promotion
Runtime verification
Failure model
Recover, do not guess
Routing Model

The application asks for an outcome. The Router owns the execution plan.

Universal Router separates the user-facing contract from network- and provider-specific mechanics. It discovers eligible sources, compares execution supply and locks a plan against the requested recipient outcome.

01

Provider tender, not provider lock-in.

Multiple providers can compete for the same intent. The Router evaluates capability, route economics, gas requirements and execution maturity instead of hard-coding one provider into the product.

CAPABILITY GATEDECONOMIC NORMALIZATIONFALLBACK READY
02

Normalize the real payer cost.

Provider fees, bridge costs, gas policy, sponsorship recovery and platform fees are normalized around the final recipient outcome and maximum user debit.

MAX DEBITEXACT OUTPUTALL-IN COST
03

Runtime capability verification.

A provider being integrated is not the same as a route being proven. Routes remain gated until the relevant quote, prepare, execution, status and recovery behavior has evidence for that profile.

VERIFIEDCERTIFICATIONFAIL CLOSED
04

Recovery is part of execution.

Unknown post-submit states are not treated as permission to send again. Idempotency, status resolution and fund-location logic are part of the Router lifecycle.

IDEMPOTENCYSTATUSRECOVERY
A payload is not the same thing as a proven route. Quote and prepare data are useful evidence, but route promotion requires runtime behavior to match the locked execution contract.
Provider Network

Different providers expose different capabilities. The Router normalizes them.

Provider status is intentionally not binary. A provider can be verified for one route profile and remain in certification for another. Capability labels explain why each supply source exists behind the tender.

Relay
Reference execution rail
VERIFIED
BridgeSwapExact-outputExact-inputStatusRefundRecoveryIdempotency
Avail Nexus
Multi-input exact-output solver
VERIFIED ROUTE
Multi-inputExact-outputSingle payoutBridgeSponsored permitRecovery model
LI.FI
Cross-chain execution supply
CERTIFICATION
BridgeSwapExact-outputExact-inputFee routingRecovery
deBridge
Cross-chain execution supply
CERTIFICATION
BridgeSwapExact-outputExact-inputPrepareStatus
Across
Intent bridge
CERTIFICATION
Intent bridgeExact-outputPrepareStatusLocate fundsApp fee
0x
Cross-chain + gasless swap profiles
CERTIFICATION
Cross-chainExact-inputExact-output*Gasless swapApp fee*Status
NEAR Intents
Cross-VM intent execution
CERTIFICATION
Exact-outputSwapBridgeStatusLocate fundsRefundRecoveryApp fee
Direct Network
Router-native wallet execution
PROFILED
Same-chainExact-outputDirect transferUser-native gasSmart-account gates
* Capability maturity is route-specific. For example, 0x cross-chain exact-output and EVM-origin fee collection are still certification-scoped, while its exact-input swap/gasless capabilities are further along. Provider cards describe useful supply, not blanket production readiness.
Provider names describe technical integrations and capability evidence. They do not imply a formal partnership or endorsement.
Execution & Resource Layers

Gas and resource orchestration are selected separately from execution supply.

A paymaster, fee payer or TRON resource gateway is not treated as another bridge. Router composes the execution provider with an eligible gas/resource policy for the locked route.

RouterPay TRC20
TRON Energy / Bandwidth resource gateway
VERIFIED
USDT TRONEnergyBandwidthExact-outputGas sponsorshipApp fee
Solana Terminal
Router fee-payer terminal execution
VERIFIED
USDC / USDTExact-outputFee payerNo user SOLRecovery
Pimlico
ERC-4337 paymaster / bundler layer
CERTIFICATION
PaymasterBundlerNexus smart accountBSC prepare proofGas recovery
MegaFuel
Scoped BSC EOA sponsor fallback
VERIFIED SCOPE
BSCZero-user-BNB profileApproval sponsorProvider-call sponsorFallback only
One Intent API

One application contract across execution rails.

Applications describe the target outcome and constraints. Provider- and network-specific execution remains behind the Router boundary.

API

The intent stays stable while supply changes underneath.

Wallets and payment applications do not need separate product logic for every bridge, gas sponsor or network-specific execution adapter.

✓Recipient, asset, destination network and requested output are explicit.
✓Source mode can remain single-source or allow compatible multi-input execution.
✓The returned plan carries debit, expiry and authorization constraints.
✓Status, receipt and recovery remain attached to the same operation.
✓Lifecycle endpoints use service authentication through the product backend; user authorization and signing remain client-side.
POST /v2/intent
{
"recipient": "0x…",
"receive": {
"asset": "USDC",
"network": "BASE",
"amount": "120.00"
},
"source_mode": "MULTI_CHAIN",
"amount_mode": "EXACT_OUTPUT"
}
router → DISCOVER
router → TENDER
router → LOCKED_PLAN
app → USER_AUTHORIZATION
router → SETTLED or RECOVERY
Lifecycle

Discover → Tender → Normalize → Execute → Recover.

The lifecycle makes execution maturity explicit. Supply can change, but the application-facing operation remains coherent from intent to receipt.

01

Discover

Find balances, supported assets, candidate networks and route-specific eligibility.

02

Tender

Ask eligible providers for executable supply instead of binding the product to one provider.

03

Normalize

Compare recipient outcome, total payer debit, gas path, expiry and execution evidence.

04

Execute

Run the locked plan only after user authorization and the required pre-submit checks.

05

Recover

Resolve unknown or partial states against the same operation instead of blindly submitting again.

Execution Networks

One intent layer. Multiple execution networks.

Universal Router normalizes network-specific signing, gas, provider and settlement mechanics behind one outcome-oriented execution model.

BASE
VERIFIED

Base

Verified source and destination profiles, including the settled Base + Arbitrum USDC multi-input route.

Profile status, not blanket coverage.
ARB
VERIFIED

Arbitrum

Verified source participation in the settled multi-input profile, with additional provider routes under certification.

Runtime evidence exists for scoped routes.
BNB
SCOPED VERIFIED

BNB Chain

Live BSC sponsorship and settlement profiles exist alongside EIP-7702 / ERC-4337 smart-account integration.

Broader smart-account submit + recovery remain certification-gated.
TRON
PROFILE-SPECIFIC

TRON

Same-chain USDT resource execution is REAL_VERIFIED. TRON-origin cross-chain execution is PARTIAL_VERIFIED.

Broader source and destination profiles remain certification-gated.
SOL
VERIFIED

Solana

Same-token terminal payments with Router fee payer are mainnet verified.

Verified profile does not require native SOL from the user.
ETH
CERTIFICATION

Ethereum

Direct, bridge, intent and smart-account capable supply is integrated behind route-specific gates.

Broader runtime promotion remains profile-specific.
OP
CERTIFICATION

Optimism

Eligible across multiple provider families with exact-output and gas-aware tender support.

Execution maturity varies by provider profile.
POL
CERTIFICATION

Polygon

Integrated across direct, cross-chain and intent supply with runtime capability gates.

Not every provider path is promoted.
AVAX
CERTIFICATION

Avalanche

Integrated into provider discovery and common origin execution models.

Runtime evidence is still being expanded.
BTC
LIMITED LIVE

Bitcoin

Native P2WPKH / PSBT execution is implemented behind an operator gate.

Production promotion remains route-specific and certification-gated.
Network badges describe the maturity of concrete route profiles. Universal Router does not imply that every provider, asset pair or execution mode on a network has the same certification state.
BNB Chain Execution · Scoped live proofs

BNB Chain without exposing gas and execution complexity.

Universal Router treats BNB Chain as an execution rail that can participate as a source or destination inside the same intent lifecycle used across the rest of the Router. Scoped mainnet sponsorship and settlement profiles are already proven; broader smart-account submission and recovery remain certification-gated.

Wallet / Appuser-controlled signer
Intentrecipient + exact outcome
Capability Checkroute + account model
Provider Tendereligible execution supply
Gas Policynative / paymaster / sponsor
BNB Executionlocked call path
Status / Recoverysame operation
EXACT OUTPUT GAS ABSTRACTION PROVIDER NEUTRAL NON-CUSTODIAL RECOVERABLE
7702

Execution architecture

BNB integration combines smart-account / EIP-7702-compatible execution, ERC-4337 bundler and paymaster paths, provider capability checks, exact-output constraints and user authorization. Separately, a scoped MegaFuel + LI.FI BSC→Base profile already has mainnet sponsored execution and settlement evidence. Smart-account submit and recovery are still fail-closed until certified.

SMART ACCOUNTEIP-7702ERC-4337FAIL CLOSED
GAS

Gas abstraction is a route policy.

The Router selects an eligible gas policy at route level. The application should not require a user to manually choose a bundler, paymaster or sponsor just to execute the intended payment.

Pimlico
paymaster / bundler path · prepare verified, broader submit certification-gated
MegaFuel
scoped BSC EOA sponsor fallback · mainnet route proof exists, not default tender path
User native BNB
valid competing policy where native gas is available and required
Execution Status Model

Execution is a state machine, not a quote response.

Applications receive one operation that progresses through explicit states. Unknown post-submit conditions move into recovery rather than being interpreted as permission to retry blindly.

Quote

Candidate economics and capability evidence are available.

Prepared

The locked signing / transaction payload matches the intended route constraints.

Authorized

User authorization is bound to the locked plan.

Submitted

Execution has crossed the broadcast / provider submission boundary.

Settled

Destination outcome and required receipts are verified.

Recovery

Unknown, partial or failed states are resolved against the same operation.

A quote proves that supply can be described. It does not prove that the route can be safely executed end-to-end. Universal Router promotes profiles based on runtime evidence, not optimistic API shape.
Security / Authorization Model

Coordinate execution without taking custody of the user's keys.

The Router is designed to own routing and state transitions, not private keys or a server-side omnibus customer balance.

◇

User-controlled authorization.

The Router does not receive private keys. The intent fixes the recipient, output asset, destination network, output amount and debit constraints before execution proceeds.

✓Private keys stay outside the Router.
✓Signing is requested against a locked execution boundary.
✓Server-side wallet signing is not required for the client-owned flow.
↻

Idempotency before retry.

Once submit may have happened, the safe action is to resolve state. The Router records the operation identity, checks provider / chain status and recovers the existing execution path.

✓Duplicate submit is not the default retry mechanism.
✓Unknown states enter status / recovery.
✓Receipt evidence remains attached to the same operation.
Verified Route Profile

Base + Arbitrum USDC → exact-output Base payment.

This is a concrete runtime-verified composition, not a statement that Universal Router only exists for Base. The profile demonstrates two compatible source balances participating in one intent and one final recipient payout.

LIVE SETTLED
Sources
Base USDC + Arbitrum USDC
multi-input · same user intent
→
Destination
Exact USDC · Base
one recipient · one final payout
Amount mode
EXACT OUTPUT
Provider
Avail Nexus profile
Verification
Runtime settled
Accounting
Cash reconciled
Use Cases

Expose one outcome model across different products.

The Router is a standalone infrastructure product. Universal Card is one client of the same intent and execution model.

W

Wallets

Let a user choose what should arrive while routing across eligible balances, networks and providers underneath.

P

Payment apps

Keep recipient settlement fixed while the Router evaluates execution supply and total payer debit.

API

Embedded routing

Integrate one intent lifecycle instead of reproducing provider-specific quote, gas, submit and recovery logic in every product.

Reference Client — Universal Card

One intent infrastructure, exposed as a simple consumer flow.

Universal Card demonstrates how the same Router can be presented to a consumer: choose the outcome, review the debit, authorize once and track one operation through settlement or recovery.

Universal Card is currently in development. Universal Router is built and running; additional routes promote as runtime certification completes.
User choosesExact outcome
Router returnsLocked plan + max debit
AuthorizationOne user-controlled signing session
OperationOne status / recovery lifecycle