AI100WEB
TON · A2A · MCP · x402 · Staging

TON for agents: A2A + MCP on TON

TON สำหรับเอเจนต์: เชื่อม A2A และ MCP เข้ากับบล็อกเชน TON

A short, source-linked map from TON concepts in docs.ton.org to what the AI100WEB gateway actually does today. Each section states the TON fact, links the page it comes from, and then says where it shows up in AI100WEB — or that it does not.

สรุปแนวคิดหลักจากเอกสาร TON อย่างเป็นทางการ แต่ละหัวข้อมีลิงก์แหล่งที่มา และบอกว่าแนวคิดนั้นอยู่ตรงไหนในระบบ AI100WEB

SIMULATION / โหมดจำลอง — This staging site signs no TON transaction, connects no wallet and accepts no real funds. x402 payments are simulated. TON reads below are read-only. staging นี้ไม่เซ็นธุรกรรม ไม่เชื่อมกระเป๋า และไม่รับเงินจริง
On this page · ในหน้านี้
  1. Accounts & async messages
  2. Wallets V4 / V5 (W5)
  3. Agentic wallets
  4. TON DNS & .ton
  5. Jettons & NFTs
  6. Payments & fees
  7. TON Connect
  8. TON APIs
  9. AI agents & MCP
  10. Verify it yourself

01 TON basics: accounts, contracts, async messages

พื้นฐาน TON: ทุกบัญชีคือสัญญาอัจฉริยะ และสื่อสารกันด้วยข้อความแบบอะซิงโครนัส

What TON does

  • Every valid address is an account with its own state and balance. There is no EOA/contract split: a wallet is itself a smart contract that checks the owner's signature and forwards messages.
  • A TON transaction changes one account while processing one message. A multi-contract call is a trace — a chain of transactions that settle one after another, not one atomic step.
  • Get-methods are free off-chain reads; a contract cannot call another contract's get-method on-chain.
  • Workchains split into shardchains when load rises and merge when it falls (“infinite sharding”); shards exchange messages via hypercube routing.

Where it shows up in AI100WEB

  • Balance and DNS skills use get-style reads through public indexers — nothing is sent on-chain.
  • x402 verification looks for a confirmed payment event rather than assuming a result the moment a message is sent, which matches TON's asynchronous model.
  • The gateway itself is off-chain: A2A JSON-RPC 2.0 requests are authenticated with Ed25519-signed envelopes, not with TON transactions.

Sources: From Ethereum · Messages & transactions · Sharding

02 Wallets V4 and V5 (W5)

กระเป๋าเงินบน TON เป็นสัญญาอัจฉริยะ แต่ละเวอร์ชันมีรูปแบบข้อความและการป้องกันการเล่นซ้ำของตัวเอง

Selected rows from the docs' wallet comparison
FeatureV5 (W5)V4
Replay protectionseqno + valid_untilseqno
Messages per requestup to 255up to 4
Gasless transferssupportedno
Plugins / extensionsextensions (delegation, recovery)plugins
SignatureEd25519 over the external message body

Most wallet apps create Wallet V5R1 accounts by default. V5 also stores a wallet_id derived from the network id (mainnet −239, testnet −3) so a signed message cannot be replayed on another network.

In AI100WEB: the Agentic Wallet (wallet v5r1 owner, x402 pay-to; holds the Agentic Wallet SBTs) UQBzg5yX7h5m-DLINTeWzxc5lwmPjJrgMtWisw4rRUDYdSXZ has the wallet_v5r1 interface (read-only check via tonapi.io, recorded in the Agent Card on 2026-10-28). The website never signs for it. The A2A layer borrows the same idea — Ed25519 signature + timestamp window + single-use nonce — at the HTTP level.

Sources: Wallet comparison · Wallet V5

03 Agentic wallets developer preview

กระเป๋าสำหรับเอเจนต์: เจ้าของกำหนดกุญแจผู้ปฏิบัติงาน และเพิกถอนได้ทุกเมื่อ

What the docs describe

  • Each agentic wallet is a soul-bound token (SBT) in a shared NFT collection, with full Wallet V5 functionality.
  • It stores the owner address, an operator public key and a nonce for replay protection.
  • The owner can withdraw, rotate the operator key, or revoke it (set it to zero). Risk is capped at what was deposited.
  • Marked by the docs as a developer preview, not audited.

Sources: Agentic wallets · SBT

In AI100WEB

Agentic Wallet
UQBzg5yX…YdSXZ (wallet v5r1 owner, x402 pay-to; holds the Agentic Wallet SBTs)
Agentic wallet SBTs
2 — “AI100WEB”, “ryounoi100web”, both owned by the Agentic Wallet
Operator key on this site
none — the edge holds no TON key
Checked
2026-10-28, read-only, tonapi.io (see Agent Card x-ton)

04 TON DNS and .ton domains

ระบบชื่อโดเมนบน TON: โดเมน .ton แต่ละชื่อคือ NFT และแปลงชื่อเป็นที่อยู่กระเป๋าได้

How resolution works

  • TON DNS is a tree of DNS contracts; the root sits on the masterchain. .ton is the only first-level domain.
  • Each .ton domain is an NFT item; the resolver is its collection.
  • Lookups call the get-method dnsresolve(subdomain, category), where the category is the SHA-256 of a record name such as wallet or site.
  • Domains are renewed yearly (0.015 Gram to the domain contract) and have no grace period.

Source: TON DNS

In AI100WEB

Domains: a2aprotocol.ton · mcpprotocol.ton · ryounoi100web.ton — all three resolve to the Agentic Wallet.

The A2A skill ton-dns-resolve and the MCP tool ton_dns_resolve read the wallet record through tonapi.io (fallback: toncenter.com v3). Read-only; a lookup never registers, renews or transfers a name.

05 Jettons (TEP-74) and NFTs (TEP-62 / TEP-64)

โทเคนและ NFT บน TON ใช้สถาปัตยกรรมแบบกระจาย: หนึ่งสัญญาต่อหนึ่งผู้ถือหรือหนึ่งชิ้น

Jettons — fungible tokens

TON limits how much a single contract may store, so a jetton is not one big ledger. A jetton master keeps supply, metadata and wallet code; every holder gets their own jetton wallet contract. Stablecoins such as USD₮ are jettons.

In AI100WEB: the read-only jetton-balance skill lists jetton wallets of an address via tonapi.io. The x402 quote can name USD₮ (by its jetton master) as an alternative asset to native coin.

Sources: Jetton standard · From Ethereum

NFTs and metadata

TEP-62 NFTs use a collection contract plus one item contract per token; a transfer is a message to the item that updates its owner. TEP-64 defines token metadata. SBTs are the non-transferable variant.

In AI100WEB: .ton domains and the agentic wallet SBTs are NFT items. There is no NFT A2A skill yet; the website dashboard only reads NFT/SBT data.

Sources: NFT standard · Token metadata

06 Payments, units and fees → x402 pay-per-call

การชำระเงินและค่าธรรมเนียมบน TON และวิธีที่ x402 ของ AI100WEB ใช้รูปแบบ “ใบแจ้งหนี้ + ข้อความกำกับ”

TON facts

  • The docs now call the native coin Gram. Amounts on-chain are integers in nanograms: 109 nanograms = 1 coin.
  • A transaction pays storage, compute (gas), forwarding and action fees; the total is their sum.
  • A payment is final once included in a masterchain block; with sub-second blocks that is about one second.
  • For incoming payments the docs describe an invoice pattern: one wallet address plus a unique text comment per invoice — and warn about reused invoices, altered amounts, copied comments and dust spam.

Sources: Payments overview · Gram payments · Fees · Units · Sub-second finality

x402 in AI100WEB SIMULATION ON

Price
0.01 TON per paid call (= 10,000,000 nano units)
Paid skills
ai-analyze, ai-summarize, ai-content, ai-orchestrate
Quote
HTTP 402 with payTo, amount and a one-time nonce
Invoice comment
x402:<nonce>
Check
amount ≥ quote, correct payTo, matching comment, confirmed before expiry; nonce single-use
Staging
simulated proofs only — no real payment is requested or verified

The single-use nonce and amount check address the reuse, amount and comment-copy risks listed in the docs.

07 TON Connect not used on staging

โปรโตคอลมาตรฐานสำหรับเชื่อมแอปกับกระเป๋า — staging นี้ตั้งใจไม่ใช้

TON Connect is the standard protocol that links a dApp to a user's wallet over an end-to-end encrypted session. The app can read the address and request signatures or transactions; the wallet keeps the keys. ton_proof lets a backend verify that the user controls the connected address.

In AI100WEB: deliberately not integrated — the site connects no wallet. Browser sign-in uses a registered A2A Ed25519 key that signs a short challenge locally (WebCrypto) and returns a short-lived HttpOnly session. If wallet login is added later, ton_proof is the documented path.

Sources: TON Connect overview · ton_proof

08 TON APIs: TON Center and tonapi.io

ช่องทางอ่านข้อมูลบล็อกเชน: liteserver, TON Center API v2/v3 และ tonapi.io

  • Liteservers — direct node access, the only option that returns proofs.
  • TON Center API v2 — HTTP over a liteserver: balances, contract queries, sending messages.
  • TON Center API v3 — an indexer: traces, jettons, NFTs, history. Streaming (SSE/WebSocket) and an emulation API are also offered.
  • Without an API key TON Center allows about 1 request per second and answers 429 above the limit.

In AI100WEB: reads go to tonapi.io v2 first and fall back to toncenter.com v3. Every result names its provider and source URL, and the MCP bridge caps body and argument sizes and upstream wait time.

Sources: APIs overview · Rate limits

09 AI agents and MCP on TON

เอเจนต์ AI กับ MCP: เทียบเซิร์ฟเวอร์ @ton/mcp ทางการ กับสะพาน MCP แบบอ่านอย่างเดียวของ AI100WEB

The TON docs ship an official MCP server, @ton/mcp (alpha), that lets an agent check balances and assets, send transfers, resolve TON DNS, request swaps and manage agentic wallets. It runs over stdio, HTTP or serverless, and handles keys and signing itself. The docs also publish llms.txt and raw markdown pages for agents.

@ton/mcp (docs)AI100WEB /mcp
Purposefull wallet agentread-only bridge for A2A agents
Keysholds and uses a signing keyholds no TON key
Toolsbalances, transfers, DNS, swaps, NFTs…ton_get_balance, ton_dns_resolve
Caller authlocal process / your deploymentEd25519-signed envelope (key id, timestamp, signature)
Also via A2A—skill mcp-tool-call on /a2a

Sources: AI on TON · @ton/mcp

10 Verify it yourself

ตรวจสอบด้วยตัวเอง: คำสั่งด้านล่างอ่านอย่างเดียวและไม่ต้องใช้กุญแจ

Unsigned, read-only checks. A signed call needs a registered key — see /start.

bash · curl
# Agent Card: skills, x402 pricing, x-ton wallet + domains
curl -s https://ai100web.pages.dev/.well-known/agent-card.json | head -c 800
# Gateway + MCP descriptors (simulation flag, read-only tool list)
curl -s -H "accept: application/json" https://ai100web.pages.dev/a2a
curl -s https://ai100web.pages.dev/mcp
# An unsigned JSON-RPC call is refused (expect HTTP 401)
curl -s -o /dev/null -w "%{http_code}\n" -X POST -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"message/send"}' https://ai100web.pages.dev/a2a

On-chain view of the Agentic Wallet: Tonviewer · Docs for agents: docs.ton.org/llms.txt