Swapper AI Agent Toolkit
A deposit layer for AI assistants that fund wallets and DeFi positions with user approval.
- Source repo
- swapperfinance/swapper-toolkit
- Stars
- ★ 850
- Last updated
- 5mo ago
- License
- MIT
- FA score
- 18/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformClaude Code
- Cost
- Free, no paid service needed
- Setup effort
- Low · running in minutes
- You'll need
- Typical use
- A Claude Code user wants to deposit $100 of USDC into Aave on Base and needs a deposit link to confirm.
- Not a fit if
- Teams needing token swaps or wallet management now; both are marked Coming Soon
- Anyone wanting auto-executed transactions without browser confirmation
- Teams that must run fully offline without blockchain or payment-network settlement
- Source review
- 18/100 · Major gaps 7 safety controls not found
What does this agent do, and when should you use it?
Swapper AI Agent Toolkit is a DeFi payment toolkit for AI agents and coding assistants, with /swapper-deposit as its currently described core skill. It creates a deposit flow for wallets or DeFi protocols using card payments, wallets, or crypto transfers. The README labels /swapper-trade and /swapper-wallet as Coming Soon, so token trading and wallet creation should not be treated as currently delivered features. Developers can also embed the deposit experience with @swapper-finance/deposit-sdk and openSwapperModal(). Every transaction requires explicit user approval, and the project states that private keys are never stored or accessed.
After installation, an agent that supports the open skills standard can use /swapper-deposit for deposit, funding, top-up, or bridge requests. The skill generates a deposit link for a specified chain, token, amount, wallet address, or protocol destination; the documented example is “Deposit $100 USDC into Aave on Base,” with Base chain ID 8453, USDC, Aave, and an amount. It describes direct wallet deposits, cross-chain transfers through Chainlink CCIP, and deposits into lending, staking, and liquidity-pool protocols. Application developers can install @swapper-finance/deposit-sdk, import openSwapperModal, and provide integratorId, dstChainId, dstTokenAddr, depositWalletAddress, styles, and supportedDepositOptions to open the deposit modal.
- A Claude Code user wants to deposit $100 of USDC into Aave on Base and needs a deposit link to confirm.
- A team building an AI finance assistant detects that a target wallet lacks funds before a strategy is run.
- A multi-chain user needs to bridge assets through Chainlink CCIP into a specified wallet or DeFi protocol.
- A product developer wants to embed openSwapperModal() in an application using @swapper-finance/deposit-sdk.
- A user wants to fund a DeFi position through a card, Apple Pay, Google Pay, or a crypto transfer.
How do you install or deploy this agent?
In an environment that can run npx, execute: npx skills add swapperfinance/swapper-toolkit. The repository does not document required accounts, API keys, a Node.js version, or post-install configuration.
How do you use this agent?
In an agent that supports the open skills standard, submit a specific deposit request such as: Deposit $100 USDC into Aave on Base. For SDK use, run npm i @swapper-finance/deposit-sdk, import openSwapperModal, and supply integratorId, destination chain ID, destination token address, and depositWalletAddress. The repository does not explain how to obtain integratorId. The user confirms the transaction in a browser.
What are this agent's strengths and limitations?
- Offers two concrete integration paths: an agent skill for assistant workflows and an SDK for embedded deposit experiences.
- The documented deposit skill spans direct wallet funding, protocol deposits, and Chainlink CCIP cross-chain transfers.
- Transactions require explicit confirmation, and the project states that it neither stores nor accesses private keys while surfacing fees, slippage, and risks before confirmation.
- Token swaps and wallet management are marked Coming Soon, so they are not safe current adoption assumptions.
- The repository does not document credential setup, integratorId provisioning, runtime versions, or a complete configuration flow.
- Operation depends on networked payment and blockchain settlement plus user confirmation in a browser; transactions are not auto-approved.
How does this agent compare with similar options?
The repository presents two delivery boundaries: /swapper-deposit for AI assistants supporting the open skills standard, and @swapper-finance/deposit-sdk for developers embedding a deposit modal in their own application.
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Swapper AI Agent Toolkit This agent | 18 · Major gaps | CLIFree | ★ 850 | 5mo ago | — | Claude Code |
| Solana Agent Kit | 42 · Major gaps | Library / SDKFree + model costs | ★ 1.7k | 4mo ago | TypeScript | OpenAI API |
| Tokless | 57 · Major gaps | CLIFree | ★ 279 | 14d ago | Go | Codex · Claude Code |
| AgentKit (Coinbase Developer Platform's AI Agent Crypto Wallet Toolkit) | 44 · Major gaps | CLIFree + model costs | ★ 1.3k | 23d ago | TypeScript | OpenAI API |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence: README claims 'every transaction requires user approval' and 'private keys are never stored or accessed', but no implementation details or code evidence provided. Deductions: lack of actual code or config to verify claims; no permission model, data flow, or sensitive data handling specifics.
Evidence: README and package.json are consistent in skill names and descriptions. Deductions: no tests or error handling documentation; dependencies not listed, availability cannot be assessed.
Evidence: README lists multiple AI frameworks and scenarios like deposit, bridge, trade. Deductions: capability boundaries vague, 'coming soon' features not implemented; trigger conditions generic, no precise trigger words or conditions.
Evidence: README, LICENSE, package.json present, simple install command. Deductions: missing changelog, version history, known limitations; maintenance responsibility unclear; information architecture simple, no detailed docs.
Evidence: README provides usage examples and SDK integration code. Deductions: no actual run evidence, output usability cannot be assessed; value proposition unverified; cost-benefit not discussed.
Evidence: README claims lack links to verifiable sources or tests. Deductions: no test results or independent verification; facts and inferences not separated.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- Repository contains only README and package.json, no actual code or tests, all feature claims unverified.
- README claims support for many frameworks and chains but provides no implementation details, may be exaggerated.
- Security claims (e.g., user confirmation, private key safety) lack code evidence, treat with caution.