Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
PayGents
Accept crypto payments in AI agent conversations. Generate MetaMask/Trust Wallet deeplinks, verify transactions on-chain, check balances, issue receipts. No...
skill openclawclawhub Free
Accept crypto payments in AI agent conversations. Generate MetaMask/Trust Wallet deeplinks, verify transactions on-chain, check balances, issue receipts. No...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, config.example.json, references/evm-usdc-poc.md, scripts/evm-balance.sh, scripts/evm-payment-link.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.3.0
Provenance
- Publisher
- AmitayBohadana
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
PayGents
Accept crypto payments through your AI agent. Generate wallet deeplinks, verify on-chain, issue receipts β no backend, no API keys.
Quick Start
Send 10 USDC on Base: scripts/evm-payment-link.sh --to 0xRECIPIENT --amount 10 --chain-id 8453 Verify the payment: scripts/evm-verify-tx.sh --chain-id 8453 --from 0xSENDER --to 0xRECIPIENT --asset ERC20 --amount 10 --blocks 50 Check a wallet balance: scripts/evm-balance.sh --address 0xADDRESS That's it. No API keys, no backend, no custody.
Flow
Agent collects payment details (recipient, amount, chain, token). Agent runs the link generator script β gets a MetaMask deeplink. Agent sends the link to the user. User taps β MetaMask opens with pre-filled transfer β user approves. User confirms "sent" β agent verifies the tx on-chain.
Wallet Detection
Before generating a link, the agent should know which wallet the user has. Ask once, remember forever. Supported wallets with native deeplinks: Wallet--wallet flagDeeplink formatMetaMaskmetamask (default)https://link.metamask.io/send/...Trust Wallettrusthttps://link.trustwallet.com/send?... Not supported (no send deeplinks): Rabby β only has in-app browser, no direct send deeplink Coinbase Wallet β only has dapp browser deeplink, no direct send Phantom β requires encrypted handshake, not a simple URL If the user's wallet isn't supported, default to MetaMask (most common) or let them know. Store the user's wallet preference so you don't ask again. The agent should note the preference in its local session context (e.g. memory file). The user can change or clear this at any time by telling the agent.
Inputs Required
FieldRequiredDescription--toYesRecipient address (0x...)--amountYesHuman-readable amount (e.g. 1.5)--chain-idNoChain ID (default: 8453 Base)--assetNoETH or ERC20 (default: ERC20)--tokenNoERC20 contract address (auto-detected for USDC on known chains)--decimalsNoToken decimals (default: 6 for USDC, 18 for ETH)--symbolNoToken symbol for display (default: USDC or ETH)--walletNometamask or trust (default: metamask)
Generate Payment Link
ERC20 (USDC) β MetaMask: scripts/evm-payment-link.sh \ --to 0x1234...5678 \ --amount 10 \ --chain-id 8453 Native ETH β Trust Wallet: scripts/evm-payment-link.sh \ --to 0x1234...5678 \ --amount 0.01 \ --asset ETH \ --chain-id 11155111 \ --wallet trust Output is JSON with: intent β structured payment details deeplink β MetaMask deeplink URL messageTemplate β ready-to-send message for the user
Verify Transaction
After the user says "sent", verify on-chain: scripts/evm-verify-tx.sh \ --chain-id 11155111 \ --from 0xSENDER \ --to 0xRECIPIENT \ --asset ETH \ --amount 0.001 \ --blocks 50 Returns the matching tx hash if found, or "not found".
Supported Chains
ChainIDDefault USDCEthereum10xA0b86991c6218b36c1d19d4a2e9eb0ce3606eb48Base84530x833589fCD6eDb6E08f4c7C32D4f71b54bDa02913Sepolia111551110x1c7d4b196cb0c7b01d743fbc6116a902379c7238Base Sepolia845320x036CbD53842c5426634e7929541eC2318f3dCf7e
User Message Pattern
When sending the link, always include: Amount + token + chain Recipient (truncated) "Tap to open MetaMask and approve" "Reject if recipient or amount doesn't match"
Check Wallet Balance
Query native + major ERC20 balances across all supported chains: # All chains at once scripts/evm-balance.sh --address 0x1234...5678 # Single chain scripts/evm-balance.sh --address 0x1234...5678 --chain-id 8453 Returns JSON with native balance + USDC, USDT, WETH, WBTC, DAI per chain. Supported chains: Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Sepolia, Base Sepolia. No API key needed β uses public RPCs directly.
Generate Receipt
After a transaction is verified, generate a structured receipt: scripts/evm-receipt.sh \ --tx-hash 0xabc123... \ --chain-id 8453 \ --memo "order-42" \ --merchant "Cool Store" Options: --format json | markdown | both (default: both) --out <directory> β save receipt files to disk (JSON + markdown) --memo β order ID or note --merchant β merchant/payee name Output includes: status, amount, token, from/to, gas fee, block, explorer link, timestamp. The receipt can be sent to the user as a confirmation message, saved for bookkeeping, or forwarded to a merchant.
RPC Configuration
By default, scripts use public RPC endpoints. You can override them for privacy or reliability: Option 1 β Environment variables (highest priority): export RPC_1="https://my-private-eth-node.com" export RPC_8453="https://my-base-rpc.com" Option 2 β Config file (copy config.example.json β config.json): { "rpc": { "1": "https://my-private-eth-node.com", "8453": "https://my-base-rpc.com" } } Option 3 β Public fallbacks (default, no setup needed): Used automatically if no env var or config is set. Public providers (e.g. eth.llamarpc.com) will see your wallet addresses and tx hashes. Resolution order: env var RPC_<chainId> β config.json β public fallback.
Security & Privacy
The wallet is the trust boundary β agent cannot force-execute. Verification checks the actual on-chain receipt, not user claims. Never store or handle private keys. RPC privacy: If using public fallback RPCs, third-party providers will see wallet addresses and tx hashes you query. Set your own RPCs via env vars or config.json for privacy. Wallet preference: The agent may store the user's preferred wallet (metamask/trust) in its memory. This is only the wallet app name, no keys or sensitive data. The user can ask the agent to clear it at any time.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs2 Scripts1 Config
- SKILL.md
- README.md
- references/evm-usdc-poc.md
- scripts/evm-balance.sh
- scripts/evm-payment-link.sh
- config.example.json