Swapper Toolkit: a deposit skill for AI agents, with the trading half still marked coming soon

The problem is funding, not trading

An agent that can reason about a strategy still cannot pay for it. The gap the README targets is the step before execution: getting USDC onto Base, getting it into Aave, or topping up a wallet that ran dry halfway through a task. The stated trigger list is explicit about this. The skill fires when a user asks to deposit, fund, top-up or bridge, and also when the agent itself notices a wallet has insufficient funds mid-task. That second trigger is the interesting one. It turns a funding shortfall into a recoverable condition rather than a dead end. The audience is therefore narrower than the topic list suggests. It is not aimed at traders who want an agent to run a strategy end to end. It is aimed at builders whose agents stall on an empty balance and who want a documented way to open a funding flow without leaving the assistant.

What the deposit skill actually does when it triggers

The README's worked example is the clearest description of the mechanism. A user says "Deposit $100 USDC into Aave on Base". The skill resolves that into four parameters: chain Base (8453), token USDC, protocol Aave, amount $100. It then states "Opening deposit link" and returns "Deposit link generated. Confirm in your browser." So the agent does not sign or broadcast anything. It extracts intent, maps it to a chain ID and a protocol, and hands the user a URL. The transaction happens in a browser, by the user. That is consistent with the safety section, which says every transaction requires user approval, that private keys are never stored or accessed, and that transactions are never auto-approved. The confirmation step is not a policy bolted on top; it is the shape of the flow. If you want an agent that completes a deposit without a human clicking, this design does not offer that, and the README does not pretend otherwise.

Install, then the SDK if you are embedding it

There are two entry points and they serve different people. For the agent side, the install is a single command: npx skills add swapperfinance/swapper-toolkit. The README says this works with any framework that supports the open skills standard, and names Claude Code, Cursor, Windsurf, OpenClaw, GitHub Copilot, CrewAI and AutoGPT. For developers embedding the flow in their own app, the package is separate: npm i @swapper-finance/deposit-sdk, then a call to openSwapperModal with an options object. The options shown are integratorId, dstChainId, dstTokenAddr, depositWalletAddress, a styles object with themeMode set to dark, and supportedDepositOptions as an array containing transferCrypto and depositWithCash. The example passes dstChainId as the string "8453", not a number, and dstTokenAddr as a full checksummed-looking address. Copy the types from those examples rather than assuming numeric chain IDs. Note that the README gives one example call and no error handling, no callback signature and no return value, so the modal's behaviour after it opens is not described in the material available here.

Chains, rails, and who is doing the settlement

The supported chain list in the README is Ethereum, Base, Arbitrum, Optimism, Polygon, Fast, Solana, HyperEVM, BNB Chain and Avalanche. That is ten networks, and it mixes EVM chains with Solana, so the skill is not a thin wrapper over one DEX. The funding rails are wider than crypto: the deposit skill lists card, wallet and crypto transfer, with fiat on-ramp through Mastercard, Visa, Apple Pay and Google Pay across 170 or more countries. Three named dependencies sit underneath. Chainlink CRE handles workflow orchestration for deposits, compliance and settlement. Chainlink CCIP handles cross-chain transfers and is described as covering 60 or more blockchains. Mastercard handles card processing. The practical consequence is that the compliance and settlement path is not in this repository. If your question is what happens when a card payment is declined or how a cross-chain message is verified, the answer lives with those providers, not in the toolkit's own code.

Two of the three skills are not shipped

This is the limitation that matters most, and it is stated plainly in the README rather than buried. /swapper-deposit is documented as available. /swapper-trade and /swapper-wallet both carry the marker "Coming Soon". The trade skill is scoped as same-chain swaps across major DEXs, cross-chain swaps via CCIP, route finding and slippage protection. The wallet skill is scoped as smart wallet creation with account abstraction, multi-chain setup, funding and balance checking. None of that is described as working today. For an agent that needs to move funds and then act on them, this means the toolkit currently covers the first half of the loop. You can get value in, and the README does not describe how the agent gets value out or how it holds a balance of its own. Treat the topic list on the repository, which includes dex, token-swap and trading, as a roadmap rather than a feature inventory.

How this differs from giving the agent a wallet library

The obvious alternative for an agent that needs to move crypto is to hand it a general-purpose wallet or web3 library and let it construct transactions directly. That approach keeps everything in-process: the agent builds a transaction, signs it with a key you supplied, and broadcasts. Swapper Toolkit takes the opposite position. It never touches keys, never signs, and never auto-approves, per its safety section, and it routes the user through a browser confirmation instead. The trade-off is real in both directions. A wallet library gives you composability and no vendor in the path, but you own key management, gas estimation and every failure mode. Swapper Toolkit removes key handling and adds fiat on-ramp and cross-chain bridging that a bare library does not provide, at the cost of a human click and a dependency on Chainlink and Mastercard infrastructure you cannot inspect from this repository. Neither is strictly better; they fail differently.

Maintenance, licence and what the MIT grant covers

The repository is MIT licensed, not archived, and the last push recorded is 2026-04-07. The README lists no releases, so there is no version history to read and no changelog to check before upgrading. That matters more than usual here because the install path is npx skills add against a GitHub repository rather than a pinned version from a registry. Whatever is on main is what you get. MIT means you can use, modify and redistribute the toolkit, including commercially, provided the copyright notice and permission notice travel with it. It does not cover the services the toolkit calls. Chainlink CRE, Chainlink CCIP, Mastercard card processing and the Swapper deposit flow are separate products under their own terms, and the SDK's integratorId suggests an arrangement with Swapper that the README does not spell out. Nothing here is legal advice; if you are embedding the deposit modal in a product, read the terms for the SDK and for the payment rails separately from the MIT text.

Editorial conclusion

Adopt Swapper Toolkit if your agent needs a funding step (a fiat on-ramp or a bridge into a protocol) and you are willing to have a browser open for the confirmation. Do not adopt it if your workflow depends on the agent executing swaps or creating wallets on its own, because the README marks /swapper-trade and /swapper-wallet as coming soon. Before wiring anything, verify the exact package name for the skills installer, confirm the integratorId you will pass to openSwapperModal, and check the current status of the two pending skills against docs.swapper.finance, since the README is the only contract you have here.

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. swapperfinance/swapper-toolkit on GitHub