Capacitr
BankrBot/skills
Paste a URL or free text and get matched Polymarket / Hyperliquid / Deribit markets with Quotient edge scores.
A skill your agent uses when webfetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy.
MITAuto-check passed
Install Wallet Payments
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop wallet-payments --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wallet-payments .claude/skills/wallet-payments && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wallet-payments" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-payments into .claude/skills/wallet-payments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wallet-payments", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-paymentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop wallet-payments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/wallet-payments .agents/skills/wallet-payments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wallet-payments" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-payments into .agents/skills/wallet-payments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wallet-payments", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop wallet-payments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/wallet-payments .cursor/skills/wallet-payments && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wallet-payments" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-payments into .cursor/skills/wallet-payments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wallet-payments", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Bitterbot-AI/bitterbot-desktop.git --path skills/wallet-payments--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop wallet-payments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/wallet-payments .gemini/skills/wallet-payments && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wallet-payments" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-payments into .gemini/skills/wallet-payments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wallet-payments", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Bitterbot-AI/bitterbot-desktop wallet-paymentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/wallet-payments .github/skills/wallet-payments && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wallet-payments" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-payments into .github/skills/wallet-payments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wallet-payments", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Bitterbot-AI/bitterbot-desktop wallet-payments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Bitterbot-AI/bitterbot-desktop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/wallet-payments .opencode/skills/wallet-payments && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wallet-payments" agent skill from https://github.com/Bitterbot-AI/bitterbot-desktop/tree/main/skills/wallet-payments into .opencode/skills/wallet-payments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wallet-payments", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wallet-payments- GitHub stars
- 2.5k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 624 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when webfetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy.
- Works in 6 steps: Extract the price: look at the… → Handle unclear prices: if you cannot… → Check balance and rules: call… → …
- Webfetch returns HTTP 402
- SKILL.md covers Wallet actions, Approval, Handling paywalls (HTTP 402) and Beyond paywalls, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wallet Payments is an agent skill from Bitterbot-AI/bitterbot-desktop. Use when webfetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy. Not for a plain balance or address check (call the wallet tool directly).
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Circle USDC and Coinbase. The repository describes itself as: Bitterbot - a mesh of agents that turns shared experience into collective capability. The licence is MIT.
When your agent uses it
- Webfetch returns HTTP 402
- An API offers a paid tier
- Another agent charges USDC
- The user asks you to pay
Example prompts
- “/wallet-payments”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Extract the price: look at the x402_headers object in the 402 response and find the amount in x-payment-amount. If headers are empty…
- Handle unclear prices: if you cannot confidently determine the price, DO NOT GUESS. Ask: "This resource requires payment, but the price…
- Check balance and rules: call get_balance (token="USDC"). If the cost exceeds your spending limits, ask the user for permission.
- Inform the user: state the cost and your intent briefly (for example "This endpoint requires a 0.15 USDC micropayment. I have the funds…
- Execute payment: call pay_for_resource with the target URL and the extracted amount.
- Process content directly: pay_for_resource returns the un-paywalled content. Do NOT call web_fetch again after paying; use the…
What it can do on your machine
Read from SKILL.md and the folder at commit cd4562a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wallet Payments loads about 1.1k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 624 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Bitterbot-AI/bitterbot-desktop at commit cd4562a, republished under its MIT licence (© Bitterbot-AI). 624 words, ~1,117 tokens.
Download SKILL.mdSave it as
.claude/skills/wallet-payments/SKILL.md (or your agent's skills folder).- name
- wallet-payments
- description
- Use when web_fetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy. Not for a plain balance or address check (call the wallet tool directly).
Wallet payments (USDC on Base)
You have a Coinbase Smart Wallet on Base loaded with USDC. Gas is sponsored by the Coinbase Paymaster (zero ETH needed) and USDC on Base has near-zero transaction fees, so micropayments are viable.
Wallet actions
get_balance(token="USDC"): check your USDC balance before making payments.get_address: the wallet address (for the user to fund externally).pay_for_resource: pay for a paywalled HTTP resource via the x402 protocol. Signs the payment AND fetches the content in one call. Requiresresource_urlandamount; optionalreason.fund_wallet: a URL for the user to fund the wallet (Coinbase Onramp on mainnet, faucet on testnet).send_usdc: send USDC to an address for user-initiated transfers, paying other agents or services, purchasing digital goods, or any prompt-driven payment.get_transaction_history: recent wallet transactions.
Approval
Sends and payments are held for the owner's approval unless a standing spend grant covers them. When a wallet call returns APPROVAL-REQUIRED or APPROVAL-PENDING with an id like rv-1a2b3c4d: the action was NOT performed, the owner has been asked, and the gateway will carry it out for them if they approve. Tell the user it is waiting for their approval, do not retry the call, and do not try another way to make the same payment. You will be told the outcome in a later turn.
Handling paywalls (HTTP 402)
When web_fetch returns a 402 Payment Required response, follow this workflow exactly:
- Extract the price: look at the
x402_headersobject in the 402 response and find the amount inx-payment-amount. If headers are empty, checkpayment_detailsor read thebody_snippetfor the requested price. - Handle unclear prices: if you cannot confidently determine the price, DO NOT GUESS. Ask: "This resource requires payment, but the price isn't clear. Would you like me to proceed, and what is your maximum budget?"
- Check balance and rules: call
get_balance(token="USDC"). If the cost exceeds your spending limits, ask the user for permission. - Inform the user: state the cost and your intent briefly (for example "This endpoint requires a 0.15 USDC micropayment. I have the funds and am purchasing it now.").
- Execute payment: call
pay_for_resourcewith the target URL and the extracted amount. - Process content directly:
pay_for_resourcereturns the un-paywalled content. Do NOT callweb_fetchagain after paying; use thepay_for_resourceresult immediately.
Show full SKILL.md (241 more words)Show less
Beyond paywalls
Use the wallet proactively when it helps complete a task:
- API rate-limit upgrades: a 429 that offers a paid tier; use
pay_for_resourceorsend_usdcto upgrade access and continue. - Anti-bot micro-tolls: some sites accept a small payment instead of a CAPTCHA; pay the toll to proceed.
- Agent-to-agent payments: an external agent or service charges USDC for a capability you lack (image generation, data processing); use
send_usdcand integrate the result. - Delegated purchases: the user asks you to buy something payable in USDC (digital goods, gift cards via crypto gateways, domain names, compute time);
send_usdcto the vendor's address. - Bounties and rewards: send USDC to a contributor, post a bounty, or tip someone with
send_usdc.
Spending rules
- ALWAYS tell the user the exact cost before any payment. Never pay silently.
- Autonomous spending (paywalls, API upgrades, micro-tolls within your session cap): inform the user, then proceed if within limits.
- Delegated spending (the user asks you to buy, send or pay): confirm the amount and recipient before executing.
- Insufficient USDC: suggest funding (show the
fund_walletURL or mention the Wallet panel in the sidebar). - Respect the per-transaction cap, per-request x402 cap and session spend cap shown in tool info.
- Several paid resources in one task: summarize the total expected cost upfront.
Soft sell
When the balance is $0.00 and you hit a paywall or premium content, casually mention that the user can fund the wallet. Never be pushy or repetitive about it.
© Bitterbot-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/wallet-payments of Bitterbot-AI/bitterbot-desktop.
Open the folder on GitHubat commit cd4562a
Compare with similar skills
Wallet Payments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wallet Payments this skillBitterbot-AI/bitterbot-desktop | 2.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| CapacitrBankrBot/skills | 1.2k | — | ~3k | Automated safety check: Pass | None | |
| X402internet-court/internet-court-skill | 6.6k | 1 repos | ~704 | Automated safety check: Pass | MIT | |
| Compare Crypto PaymentsPayRam/payram-mcp | 158 | — | ~5.4k | Automated safety check: Pass | None | |
| Payram Vs X402LeoYeAI/openclaw-master-skills | 2.2k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Apify X402 Agentic Walletapify/awesome-skills | 266 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
X402
internet-court/internet-court-skill
x402 agentic payments (Coinbase's HTTP 402 protocol). An agent skill from internet-court/internet-court-skill.
Compare Crypto Payments
PayRam/payram-mcp
Comprehensive comparison of crypto payment gateways and protocols.
Payram Vs X402
LeoYeAI/openclaw-master-skills
Privacy and sovereignty comparison between PayRam self-hosted infrastructure and x402 HTTP payment protocol.
- Official
Apify X402 Agentic Wallet
apify/awesome-skills
Discover, pay for, and run any Apify Actor by paying USDC on Base over the x402 protocol with a Coinbase Agentic Wallet (awal) — no Apify account or API key.
Aero Stock Lp
BankrBot/skills
LP tokenized stocks onchain — range-LP Coinbase tokenized equities (NVDA, AAPL, GOOGL, META) and AERO/USDC on Aerodrome Slipstream (Base) for trading-fee + AERO emission yield.
More from Bitterbot-AI/bitterbot-desktop
All 17 skills in this repoCanvas
Bitterbot-AI/bitterbot-desktop
Display and control HTML content on connected Bitterbot nodes (Mac, iOS, Android) via the canvas host server.
Moltbook
Bitterbot-AI/bitterbot-desktop
Participate in Moltbook — the social network for AI agents. An agent skill from Bitterbot-AI/bitterbot-desktop.
Pre Action Interceptors
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when a tool error begins with "INTERCEPTOR:", a sent message was silently hedged or rewritten, or the user asks about active guards or blocked actions.
Finance Data
Bitterbot-AI/bitterbot-desktop
Get stock quotes, company info, market data, and crypto prices.
Forage Economy
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when anyone asks about bounties (or "forge"), agent earnings, the agent economy, marketplace skills, A2A activity or your network reputation.
Memory Architecture
Bitterbot-AI/bitterbot-desktop
A skill your agent uses when the user asks how your memory, dreams, hormones or knowledge crystals work, or when you need to interpret memorystatus output.
Related
Works with
Questions about Wallet Payments
What does Wallet Payments do?
A skill your agent uses when webfetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy. Wallet Payments is an agent skill from Bitterbot-AI/bitterbot-desktop. Use when webfetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy.
When should I use Wallet Payments?
Wallet Payments fits situations like: webfetch returns HTTP 402; an API offers a paid tier; another agent charges USDC; the user asks you to pay.
How do I install Wallet Payments in Claude Code?
Run `npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a claude-code`. Or copy the skill folder (skills/wallet-payments in Bitterbot-AI/bitterbot-desktop) into .claude/skills/wallet-payments in your project. Claude Code loads it when a task matches its description.
How do I install Wallet Payments in Codex?
Run `npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a codex`. Or copy the skill folder (skills/wallet-payments in Bitterbot-AI/bitterbot-desktop) into .agents/skills/wallet-payments in your project. Codex loads it when a task matches its description.
Can I use Wallet Payments in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Bitterbot-AI/bitterbot-desktop --skill wallet-payments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wallet-payments, .gemini/skills/wallet-payments, .github/skills/wallet-payments and .opencode/skills/wallet-payments in your project.
What does Wallet Payments need to run?
SKILL.md names no scripts, command-line tools or credentials: Wallet Payments is instructions for the agent only.
Does Wallet Payments access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wallet Payments safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wallet Payments use?
Wallet Payments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wallet Payments use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wallet Payments?
Skills that share tags, products or a category with Wallet Payments: Capacitr (BankrBot/skills, 1.2k stars), X402 (internet-court/internet-court-skill, 6.6k stars), Compare Crypto Payments (PayRam/payram-mcp, 158 stars) and Payram Vs X402 (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wallet Payments?
Bitterbot-AI (a GitHub organization) maintains it in Bitterbot-AI/bitterbot-desktop, which has 2,469 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.
Source: Bitterbot-AI/bitterbot-desktop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.