Locus Payment Skill
Locus MCP provides crypto payment tools for AI agents via mcporter. Tools are dynamic β each user sees only what their permission group allows.
Setup
On first use, check if locus is configured:
mcporter config get locus 2>/dev/null
If not configured, run the setup script:
bash skills/locus/scripts/setup.sh
Or configure manually:
mcporter config add locus \
--url "https://mcp.paywithlocus.com/mcp" \
--header "Authorization=Bearer <YOUR_LOCUS_API_KEY>" \
--scope home
Get your API key at https://paywithlocus.com β each agent gets its own key tied to a wallet and permission group.
Requirements
mcporterCLI installed (npm i -g mcporter)
Discovering Available Tools
Tools are dynamically exposed based on your permission group. Always discover what's available first:
mcporter list locus --schema
Common Built-in Tools
These may be available depending on your permissions:
get_payment_context β Check budget status, balance, and whitelisted contacts.
mcporter call locus.get_payment_context
list_tokens β List approved tokens with balances and spending limits.
mcporter call locus.list_tokens
send_token β Send a token to a wallet address, ENS name, or email.
mcporter call locus.send_token token_symbol=USDC [email protected] amount=10 memo="Invoice payment"
- Wallet addresses (0x...) β direct on-chain (Base network)
- Email addresses β escrow (recipient gets email to claim)
- ENS names (vitalik.eth) β resolved on-chain
send_token_multi β Send multiple tokens to one recipient.
mcporter call locus.send_token_multi recipient=0x742d... --args '{"tokens":[{"symbol":"USDC","amount":10},{"symbol":"ETH","amount":0.01}],"memo":"Multi-token payment"}'
approve_token β Approve a smart contract to spend tokens (ERC-20 allowance).
mcporter call locus.approve_token token_symbol=USDC spender_address=0x... amount=100
x402 Tools
Your permission group may also include x402 micropayment tools β dynamically generated from approved API endpoints. These let your agent pay for and consume external APIs autonomously. Run mcporter list locus --schema to see all available tools.
Email β Payment Flow
- Scan inbox for payment-related emails (invoices, bills, splits, reimbursements)
- Identify actionable items with amounts, recipients, and context
- Summarize findings to user
- On user approval, execute payments via available send tools
- Always confirm with user before sending any payment
Safety Rules
- Never send payments without explicit user confirmation
- Always show: recipient, token, amount, and memo before executing
- Use
list_tokensfirst to verify available balance - Use
get_payment_contextto check budget limits - Double-check recipient addresses β typos mean lost funds
- Confirm large payments (>$100) with extra care