CryptoSlate
Tether CEO Paolo Ardoino framed WDK, the company's Wallet Development Kit, as programmable money for people, machines and AI agents when it launched on Nov. 11, 2024. The Sept. 3 walkthrough of WDK CLI makes that vision concrete: a local command-line wallet that hands an unlocked session over to a daemon, which another process running as the same OS user can ping for signatures without re-entering the passphrase. Default sessions last five minutes; the lock can be extended, shortened or disabled outright.
Why it matters
The CLI ships with three components: terminal commands, the background daemon, and a bundled Model Context Protocol server that lets an AI client call structured tools against the same local wallet. Locked seeds sit behind AES-256-GCM with an scrypt-derived key. Once unlocked, the daemon's socket is restricted to the OS user on macOS and Linux, but no separate credential gates each program. The MCP interface keeps wallet creation, seed export and unlocking out of its tool menu, narrowing what an agent can request through that path; transfers default to a dry run with a preview-and-confirm sequence, though the daemon does not require proof those steps ran before executing a valid request.
Tether's own division of uses places the CLI in local operator workflows, the SDK inside applications and the MCP Toolkit in custom agent servers. A second route on the bundled MCP server, call_method, can invoke declared chain-specific write operations without a dry run or enforced confirmation, which means the location of any approval check is consequential: a careful prompt means nothing if the underlying wallet still accepts requests through another permitted path.
Market impact
The SDK exposes local ALLOW and DENY transaction policies that can block governed calls, but it is opt-in and has defined gaps, including raw account references and certain internal module calls that remain outside its interception. The documentation is explicit that the SDK does not maintain recipient lists, fetch prices, decode contract-call data or persist spending counters. A daily budget illustrated the consequence: checking one payment's size cannot establish how much an agent has already spent that day, so any cumulative ceiling needs application-level accounting alongside per-payment checks. The MCP Toolkit's built-in write tools, still beta.1, use MCP elicitations for explicit user approval before broadcasting, and lets developers expose read-only tools or add their own.
Frequently asked questions
-
What is Tether's WDK and how does it relate to AI agents?
WDK is Tether's Wallet Development Kit, framed by CEO Paolo Ardoino on Nov. 11, 2024 as programmable money for people, machines and AI agents. Its CLI walks through a local wallet whose unlocked daemon can be pinged by other same-user processes, with a bundled Model Context Protocol server that lets AI clients call…
-
How does the WDK CLI protect the wallet when an AI agent is paying?
Locked seeds are encrypted with AES-256-GCM using an scrypt-derived key, and the daemon's socket is restricted to the OS user on macOS and Linux. Default sessions last five minutes. Admin actions such as wallet creation, seed export and unlocking sit outside the bundled MCP server's tool menu, and send_token defaults…
-
What spending controls does the WDK SDK give developers?
The SDK exposes local ALLOW and DENY transaction policies that can block governed wallet or protocol calls, but they are opt-in with defined gaps, including raw account references and certain internal module calls. It does not maintain recipient lists, fetch prices, decode contract-call data or persist spending…
-
What is the MCP Toolkit and how does it differ from the bundled CLI server?
The MCP Toolkit is a separate, still-beta.1 layer aimed at custom agent servers. Tether says its built-in write tools use MCP elicitations to obtain explicit user approval before broadcasting, and configuration options let developers expose read-only tools, pick individual operations or add their own.
-
Which version of WDK CLI does the documentation describe?
The current CLI guide describes release 1.0.0-beta.3, while Tether's Aug. 27 changelog records beta.4. The newer entry is a configuration-override fix; public commands, configuration keys and stored-data behavior are described as otherwise unchanged, so beta.3 should not be read as the latest.
WatcherGuru
CoinDesk
Crypto News
CoinTelegraph
TheBlock
WuBlockchain