Install
$ agentstack add skill-openagentinternet-open-agent-connect-metabot-wallet-manage ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Bot Wallet Manage
Handle wallet balance checks and BTC/SPACE/DOGE/OPCAT transfers to a target address. Treat Bot, bot, and MetaBot as equivalent user wording for the selected local wallet profile.
Routing
Route natural-language intent through $HOME/.metabot/bin/metabot, then reason over the returned JSON envelope.
- Prefer JSON and local daemon routes for agent workflows.
- Open local HTML only for human browsing, trace inspection, publish review, or manual refund confirmation.
- Treat MetaWeb as the network layer and the local host as a thin adapter.
Actor Selection
Wallet commands accept optional --from . Use it whenever the human names a specific local Bot, a previous workflow step already selected a Bot, or a transfer confirmation must use the same wallet as the preview. If --from is omitted, the CLI falls back to the active identity.
Trigger Guidance
Should trigger when:
- The user asks for wallet balance across all chains, MVC only, BTC only, DOGE only, or OPCAT only.
- The user asks to send, transfer, or pay BTC, SPACE, DOGE, or OPCAT to an address.
- The user mentions an amount with BTC, SPACE, DOGE, or OPCAT and a recipient address.
Should not trigger when:
- The user asks to publish buzz/service/file content.
- The user asks to delegate paid remote services.
- The user asks to manage network sources or identities.
Network and Currency Mapping
This is the authoritative mapping. Do not query any other API or chain for these currencies.
| User says | Network | CLI flag | Notes | | ------------------------- | ------- | ------------- | ----------------------------------------------------------------------------------------------- | | SPACE / space / 太空币 | MVC | --chain mvc | SPACE is the native currency of the MVC network. Querying SPACE balance = querying MVC balance. | | MVC / mvc | MVC | --chain mvc | Same network as SPACE. | | BTC / btc / Bitcoin / 比特币 | Bitcoin | --chain btc | | | DOGE / doge | Dogecoin | --chain doge | Use DOGE as the transfer amount unit. | | OPCAT / opcat | OPCAT | --chain opcat | Use OPCAT as the transfer amount unit. |
Never search for a separate SPACE API, SPACE contract, or FT token endpoint. SPACE is not a token — it is the base currency of the MVC network and is always returned by wallet balance --chain mvc.
Balance Command
For default multi-chain balance (MVC/SPACE + BTC + DOGE + OPCAT):
$HOME/.metabot/bin/metabot wallet balance --from
When the human asks for BTC, Bitcoin, or 比特币:
$HOME/.metabot/bin/metabot wallet balance --from --chain btc
When the human asks for DOGE or Dogecoin:
$HOME/.metabot/bin/metabot wallet balance --from --chain doge
When the human asks for OPCAT:
$HOME/.metabot/bin/metabot wallet balance --from --chain opcat
When the human asks for SPACE, MVC, 太空币, or any MVC-network currency:
$HOME/.metabot/bin/metabot wallet balance --from --chain mvc
The mvc balance response includes balances.mvc.totalMvc (the SPACE amount) and balances.mvc.address (the MVC/SPACE receiving address). DOGE and OPCAT balances are returned under balances.doge and balances.opcat.
Default Write Network Config
Wallet balance and transfer do not use the default write-network setting. Balance defaults to all chains, and transfer selects the chain from the amount unit (BTC, SPACE, DOGE, or OPCAT).
Use these commands only when the human asks to inspect or change the default chain for on-chain write commands such as buzz, service publish, rating, private chat, or generic chain write:
$HOME/.metabot/bin/metabot config get --from chain.defaultWriteNetwork
$HOME/.metabot/bin/metabot config set --from chain.defaultWriteNetwork opcat
Supported values are mvc, btc, doge, and opcat. The setting is scoped to the selected local Bot profile.
Transfer Command
Currency mapping (same as balance — see Network and Currency Mapping above):
BTC→ Bitcoin network (--amount 0.00001BTC)SPACE→ MVC network (--amount 1SPACE). SPACE is the native currency of MVC; useSPACEas the unit, notMVC.DOGE→ Dogecoin network (--amount 0.01DOGE)OPCAT→ OPCAT network (--amount 10OPCAT)
Amount format: append the currency unit directly to the number, no space required.
0.00001BTC— send 0.00001 BTC1SPACE— send 1 SPACE (MVC)0.01DOGE— send 0.01 DOGE10OPCAT— send 10 OPCAT- Amounts are case-insensitive:
1space,0.00001btc, and10opcatare all valid.
Step 1 — Always preview first (no --confirm)
Run the transfer command without --confirm to get a preview. Never skip this step.
$HOME/.metabot/bin/metabot wallet transfer --from --to --amount
Example — preview a BTC transfer:
$HOME/.metabot/bin/metabot wallet transfer --from --to 1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 0.00001BTC
Example — preview a SPACE transfer:
$HOME/.metabot/bin/metabot wallet transfer --from --to 1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 1SPACE
Example — preview an OPCAT transfer:
$HOME/.metabot/bin/metabot wallet transfer --from --to o1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 10OPCAT
Example — preview a DOGE transfer:
$HOME/.metabot/bin/metabot wallet transfer --from --to D9UuD6sjdEUNv8hPC8WtUXZapBCsFn67jo --amount 0.01DOGE
The response has state: "awaiting_confirmation" and data containing:
fromAddress— sender addresscurrentBalance— total spendable balance including both confirmed and unconfirmed UTXOs (e.g."0.001 BTC")toAddress— recipient addressamount— exact amount to sendestimatedFee— estimated network feefeeRateSatPerVb— fee rate usedcurrency/chain
Present this information clearly to the human and ask for explicit approval before proceeding.
Step 2 — Execute only after human confirms
After the human explicitly approves, re-run the same command with --confirm appended:
$HOME/.metabot/bin/metabot wallet transfer --from --to --amount --confirm
Example:
$HOME/.metabot/bin/metabot wallet transfer --from --to 1EX5NN6npyCp3X6Sv4Yahv6DrBNKRtq4Gw --amount 0.00001BTC --confirm
On success the response contains:
txid— transaction IDexplorerUrl— clickable link to view the transaction on the block exploreramount— amount senttoAddress— recipient
Always show the explorerUrl to the human so they can verify the transaction on-chain.
Natural language → CLI mapping examples
| User says | CLI command | | ------------------------------- | ---------------------------------------------------------------------- | | "帮我往地址1EX5NN...转账 0.00001 BTC" | wallet transfer --from --to 1EX5NN... --amount 0.00001BTC | | "给地址1EX5NN...转 1 SPACE" | wallet transfer --from --to 1EX5NN... --amount 1SPACE | | "send 0.0001 btc to 1EX5NN..." | wallet transfer --from --to 1EX5NN... --amount 0.0001BTC | | "transfer 5 space to 1EX5NN..." | wallet transfer --from --to 1EX5NN... --amount 5SPACE | | "transfer 0.01 doge to D9UuD..." | wallet transfer --from --to D9UuD... --amount 0.01DOGE | | "transfer 10 opcat to o1EX5..." | wallet transfer --from --to o1EX5... --amount 10OPCAT |
Error Handling
- insufficient_balance — show the current balance and tell the user how much more is needed. UTXOs are spendable regardless of confirmation status — the total balance is what determines whether a transfer can proceed.
- invalid_argument — the address or amount format is wrong; ask the user to correct it.
- transferbroadcastfailed — the network rejected the transaction; show the error message. If the error mentions mempool conflict, wait a few seconds and retry — the conflict usually resolves on its own.
In Scope
- Wallet balance checks across all, MVC, BTC, DOGE, or OPCAT chains.
- BTC, SPACE (MVC), DOGE, and OPCAT transfers with two-step preview + confirm flow.
Out of Scope
- On-chain social/service publish writes.
- Remote service order lifecycle.
- Identity or network source management.
- Other chain transfers.
Handoff To
metabot-post-buzz/metabot-upload-file/metabot-post-skillservicefor publish flows.metabot-call-remote-servicefor service delegation.metabot-network-managefor network discovery/source operations.
Compatibility
- CLI path:
$HOME/.metabot/bin/metabot - Compatibility manifest:
release/compatibility.json
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: openagentinternet
- Source: openagentinternet/open-agent-connect
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.