How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/ton-org/kit --skill ton-create-walletBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Create TON Agentic Wallet
Deploy an on-chain agentic wallet on TON. The agent generates operator keys, opens the dashboard when local browser/shell tools are available, and uses callback-based completion only in long-lived stdio/HTTP MCP server sessions.
MCP Tools
| Tool | Description |
|---|---|
agentic_start_root_wallet_setup | Generate operator keys, create pending setup, return dashboard URL |
agentic_list_pending_root_wallet_setups | List pending setup drafts and their callback status |
agentic_get_root_wallet_setup | Read one pending setup by setupId |
agentic_complete_root_wallet_setup | Finish onboarding from callback or manual wallet address |
agentic_cancel_root_wallet_setup | Cancel a pending setup |
Tool Parameters
| Tool | Required | Optional |
|---|---|---|
agentic_start_root_wallet_setup | — | network, name, source, collectionAddress, tonDeposit |
agentic_get_root_wallet_setup | setupId | — |
agentic_complete_root_wallet_setup | setupId | walletAddress, ownerAddress |
agentic_cancel_root_wallet_setup | setupId | — |
Workflow
- Call
agentic_start_root_wallet_setup— this generates an operator key pair and returns asetupId,dashboardUrl, andcallbackUrl - If the environment exposes local browser or shell tools, open
dashboardUrlyourself with the platform opener (open,xdg-open,start) or browser automation; only paste the link to the user if automatic opening is unavailable or fails - Tell the user only to approve wallet deployment from their main TON wallet; do not ask them to retype the URL or copy intermediate data
- In long-lived stdio/HTTP MCP server sessions, poll
agentic_get_root_wallet_setuporagentic_list_pending_root_wallet_setupsand wait forstatus: "callback_received"when callback flow is available; then callagentic_complete_root_wallet_setupwithsetupId; - In raw one-shot CLI usage, skip callback polling and ask for
walletAddressafter the user deploys the wallet; then callagentic_complete_root_wallet_setupwithwalletAddress - Confirm the wallet is active with
get_current_walletorlist_wallets(seeton-manage-walletsskill)
How It Works
- The agent keeps the operator private key — it can sign transactions autonomously
- The user keeps the owner key — they can withdraw funds or revoke access at any time
- The wallet is an on-chain smart contract (NFT-based), not a custodial service
- The dashboard is at
agents.ton.org
Environment Variables
| Variable | Description |
|---|---|
NETWORK | mainnet (default) or testnet |
AGENTIC_CALLBACK_BASE_URL | Public URL for the onboarding callback (auto in HTTP mode) |
AGENTIC_CALLBACK_PORT | Port for the callback server |
Notes
- Callback-driven completion is for long-lived stdio/HTTP MCP server sessions; raw CLI should use manual
walletAddresscompletion - If automatic dashboard opening is supported in the current environment, do it instead of asking the user to open the URL manually
- In raw CLI mode, ask for the wallet address after deployment because the callback server is not available long enough to complete the flow
- After wallet creation, fund the wallet with GRAM (ex. TON) before using transfer or swap skills
