TON launches AgentKit agent tools

TON’s agent push is easiest to understand as a stack, not a single launch. On May 19, developers on X circulated fresh attention around TON Agent Kit and related “agentic” tooling for building autonomous software agents that can hold funds, call onchain functions and pay for services. The core pieces already live in TON’s public developer stack: a TypeScript Agent Kit on GitHub, TON MCP tools for agents, and agentic wallet contracts and dashboards published in TON documentation. Wilson Betha’s X post, referenced in the story brief, framed the moment around growing developer interest in agent SDKs and pointed to TON alongside other agent projects. A direct web preview of that post was limited, but TON’s own public materials support the underlying claim that the network is assembling infrastructure for agents that can transact and operate with fewer manual approvals. (github.com) ### So what exactly did TON put in front of developers? TON Agent Kit is described in its GitHub repository as a way to “connect any AI agent to TON,” with 75 actions across 12 plugins and 21 npm modules. The repository says agents can swap tokens, deploy contracts, manage escrows, broadcast intents, discover other agents and get paid for services from a single toolkit. The same repository presents the product as “the agent infrastructure for TON” and sketches a commerce loop in which one agent registers onchain, publishes capabilities, finds services, negotiates deals, escrows funds, delivers through paid endpoints and settles with ratings. (docs.ton.org) ### How do these agents actually get money and permissions? TON’s docs say agentic wallets are self-custody wallets designed for autonomous AI agents on TON. (github.com) The contracts use a split-key setup in which the user remains the owner, while the agent operates with a separate key tied to an isolated wallet. TON’s documentation also says the user can withdraw funds, rotate the operator key or deactivate the agent at any time, while warning that an active agent still has complete control over the assets placed in its own wallet. (github.com) The docs add a prominent caution: the contracts are in developer preview, have not been audited, and should be used on testnet for experiments. ### Why are people calling this “persistent” or “self-funding”? (docs.ton.org) TON’s live Agentic Wallets site says users can fund isolated wallets for agents and let them transact autonomously while monitoring activity from a dashboard. The site lists use cases including trading bots, DeFi agents, recurring payment automation and Telegram Mini Apps with embedded agent execution. A payments component is also already public. (docs.ton.org) The npm page for `@ton-agent-kit/plugin-payments` says the plugin handles paid API access on TON using x402-style flows, including sending TON, retrying with onchain proof and receiving an unlocked response. That is the clearest public basis for the “self-funding” language used around these agents: they are being equipped to receive and spend funds directly within bounded wallets. (agents.ton.org) ### Where does $AEON fit into this conversation? AEON appears in current agent discussions as a separate autonomous-agent framework rather than a TON-native primitive documented by TON itself. A public AEON repository describes it as “the most autonomous agent framework,” with scheduled tasks, persistent operation and minimal approval loops, while the PyPI listing highlights event-sourced memory, delayed tasks and audit trails. (npmjs.com) That makes AEON relevant as an example of the type of long-running agent software that could plug into onchain rails like TON’s, but the available primary TON sources do not identify AEON as an official TON launch. ### And what about the Base example people were pairing with it? PeptAI, cited in the social chatter, is a separate Base-linked project focused on drug discovery. (github.com) Bio’s project page describes PeptAI as an autonomous AI agent that discovers peptide drug candidates through a validation pipeline and publishes results onchain, while Base’s own materials describe the chain as a low-cost builder platform for onchain apps. (github.com) The practical next stop for builders is TON’s own documentation. TON’s docs point developers to `@ton/mcp` for setup, while the Agentic Wallets dashboard and Agent Kit repository remain live for testing and integration as of May 19. (docs.ton.org) (app.bio.xyz)