We use ready-made swaps to trade crypto. Why should AI agents code every swap from scratch?
AgentSwap lets them swap tokens via x402.
Let your agent focus on its task. Let AgentSwap handle the swaps.
Use skill or:
const { response, receipt } = await agentswap.fetchWithReceipt(url, undefined, { paymentIntentId: 'purchase-42' });
Persist the ID per purchase. Configure a durable intent store to keep retry state across restarts. https://t.co/YyPzWahDrz
What did the retry reuse? AgentSwap receipts expose reusesPaymentIntent, reusesFunding and reusesAuthorization. Replaying the same authorization does not guarantee seller fulfillment exactly once; use merchant idempotency too.
An x402 seller can name the right asset and amount while your agent holds funds on another chain.
AgentSwap turns that challenge into a funding plan from Solana. The agent signs locally.
API reference: https://t.co/BYMpY7Zouy
Your agent holds SOL. The x402 seller wants USDC on Base.
AgentSwap v0.2.0 adds funding from Solana for EVM payments, with an API, SDK and MCP tool. Your agent keeps its keys.
Here's the flow. 1/8
8/8 Building an x402 agent? Try the v0.2.0 funding API or the SDK from the repo.
Send a public, non-sensitive challenge example if a route fails. Include the chain and source token.
Release and setup: https://t.co/3KBunOeXx5
7/8 We completed a real Solana -> Base -> Solana round trip: 10 USDC in, 9.895157 USDC back, plus 0.001511002 SOL spent on the source side.
That verifies the bridge round trip. Seller-payment E2E remains to be verified.