When TRANSFER_REQUIRE_CONFIRMATION=true (default), Uniswap swaps follow the same human-in-the-loop pattern as native transfers: the agent prepares an unsigned quote, the user reviews details in chat, then Confirm or Cancel.
The env var name is shared with transfers (TRANSFER_REQUIRE_CONFIRMATION). Set it to false only when you want auto-sign for both transfers and swaps.
Flow
Chat UI
The sample web app renders a Swap confirmation card with:
| Field | Example |
|---|
| Sell | 0.1 ETH |
| Buy | ~250 USDC |
| Network | base |
| Routing | CLASSIC |
| Approval | Required or not required |
PENDING_SWAP_TTL_MINUTES (default 15, max 60).
REST API
Base path: your agentic-ai API (sample: /agents).
| Method | Path | Description |
|---|
GET | /agents/:agentId/swaps/:pendingId | Fetch pending swap details |
POST | /agents/:agentId/swaps/:pendingId/confirm | Sign approval (if needed) and swap |
POST | /agents/:agentId/swaps/:pendingId/cancel | Cancel without broadcasting |
{
"status": "submitted",
"swapTxHash": "0x…",
"approvalTxHash": "0x…",
"chainId": 8453
}
SSE events
During chat streaming, the backend emits:
| Event | Purpose |
|---|
swap_pending | Structured rows + pendingSwapId for the UI |
swap_confirmation_ui | Same UI payload for dedicated listeners |
swapPending so history reloads the card without re-parsing markdown.
Environment variables
| Variable | Default | Effect |
|---|
TRANSFER_REQUIRE_CONFIRMATION | true | Enable swap confirmation UI |
PENDING_SWAP_TTL_MINUTES | 15 | Pending swap expiry |
TRANSFER_WAIT_FOR_RECEIPT | true | Wait for receipt after broadcast |
Implementing in your app
Mirror the sample web app:
- Parse
swapPending from assistant message metadata (or markdown fallback).
- Render a confirmation card with sell/buy/network rows.
- On Confirm,
POST …/swaps/:pendingId/confirm with the user JWT.
- Show
swapTxHash with a block explorer link.
Transfer confirmation uses the same pattern — see Full-stack integration.
