SwaggerMove tokens on several chains without making your users hold the chain's own coin to pay for it.
Introduction
UGTP provides one API for token transfers, swaps and private-token operations across supported networks. Token-settled rails let accounts pay fees in a supported token instead of the network's native coin.
An ordinary token transfer requires native gas, such as ETH, AVAX or BNB. A user may hold enough tokens to transfer but lack the native coin needed to submit the transaction.
On a token-settled rail, UGTP pays network gas and collects the quoted fee in a supported asset. Your integration prepares the operation, obtains the account's signature, submits it and polls its status. Native AVAX transfers use the self-funded rail and require the account to pay its own gas.
In the industry's vocabulary this is white-label wallet infrastructure — wallet-as-a-service. UGTP is an API layer over the EVM wallets your users already hold, adding two things: programmability, which turns the wallet into a smart account, and private tokens. Stablecoin settlement is the case it is built around.
Vocabulary
Nine words this documentation leans on. Each one is plain enough to read before your first call.
The account pays no native coin. Someone else puts the transaction on chain and recovers the cost from the token being moved. It does not mean free — the fee is real, it is just charged in the asset the user actually holds.
The user's ordinary wallet address. UGTP does not create a second address, a contract wallet or a deposit address: the account is the address they already have, which is why balances and block-explorer history stay where the user expects.
One thing the user asked for — a transfer, a swap, a deposit. You prepare it, the user's wallet signs it, you submit it, and it gets an operation id you poll until it is on chain. Keep the operationId to track status, alongside the transaction hash and outcome needed by your application.
The execution envelope UGTP uses on its UserOperation rail. It carries what to execute, who authorized it, and who is paying the gas. On the networks that support it, that envelope is what your user signs — you never assemble it yourself, UGTP returns it ready to sign.
The on-chain contract that agrees to pay a user operation's gas and takes its fee from the transferred token in the same transaction. It is why the user needs no native coin, and its address is published so you can verify it.
How a particular operation reaches the chain. Not every network supports the same mechanism, so UGTP picks one and tells you which — that is the single thing your client has to branch on, and it is why the same integration works everywhere.
The token the fee is taken in. Usually the token being moved, so a USDT transfer costs USDT. Each network publishes which tokens it accepts.
Exchanging one token for another. UGTP quotes a route from LI.FI, which aggregates decentralised exchanges and bridges, then prepares the route on the source network's applicable rail. Token-settled rails collect fees in tokens; a self-funded swap requires native gas. A swap can stay on one chain or end on another.
A supported public token wrapped 1:1 into an encrypted form, where the balance and the transferred amount are ciphertext on chain rather than public numbers. The encryption is AvaCloud's Encrypted ERC-20 (eERC), which UGTP runs on Avalanche C-Chain. The user deposits the public token, moves the private one with the amount hidden, and can withdraw to the public token subject to the available balance, proof and fee requirements.
Next
Three steps, in order, from understanding the model to moving a real token.
The account is the user's own address, and the rail decides what they sign. Those two ideas explain every endpoint here.
Read it →Prove the host, prove your key, and price an operation — without creating or spending anything.
Read it →Prepare, sign, submit, poll. The same four steps carry a transfer, a swap and a private-token operation.
Read it →