What MOTE actually does today.
AI agent infrastructure is being built faster than anyone can verify. Most companies in this space are going to overclaim what's live and underdeliver on what's coming. We'd rather show our work.
This page lists exactly what's running on MOTE today, what we're building, what's planned, and what we won't claim until it's real. Everything in “Live” can be verified — most of it with links to the actual endpoint or on-chain record.
Every $10 registration creates a permanent Decentralized Identifier (DID) anchored on Sui mainnet. The on-chain record is owned by the merchant's own address, not MOTE's — cryptographically inspectable by anyone.
You author a Global Context Document — your business, your services, your story, in your own voice. MOTE publishes it at human-memorable URLs in every format AI agents look for: a readable page at /m/[slug], plus /llms.txt and .json for machines. A global sitemap at mote.network/sitemap.llms.txt lists every merchant on the network in real time.
Every merchant publishes an x402 payment manifest declaring how an agent can pay them — their own Sui address as recipient, USDC as the asset. x402 is governed by the Linux Foundation, with Visa, Mastercard, American Express, Stripe, Coinbase, Google, Microsoft, AWS, Cloudflare, Shopify, and Circle as foundation members.
Fetch a real manifest →Real USDC has been sent from Base to a MOTE merchant's Sui address via NEAR Intents. No bridges, no manual gas. Any of the 20+ chains and 80+ assets NEAR Intents supports can land funds in a merchant's Sui address today.
MOTE is live on the official MCP Registry. Any MCP client — Claude Desktop included — can query MOTE's registry directly. Grok organically indexed a MOTE merchant's llms.txt without any submission required — proof the open-web discovery path works. Agents can also execute the registration procedure directly — read it at mote.network/skills/register-merchant.
Today your Sui address is created at registration and used by the system, but it isn't surfaced cleanly in your dashboard. Coming soon: copy-to-clipboard, QR, and balance display.
Agents can already read how to pay a MOTE merchant. The next step is MOTE confirming the payment landed and notifying the merchant — webhook delivery, dashboard activity, the full loop. Active engineering, weeks to months.
A view of inbound transactions, source chain, amount, time, and the agent request that triggered the payment. Pairs with verification above.
Phase 2. Agents post intent (“need a caterer for 80 people, vegetarian, London”) and MOTE routes it to the registered businesses that match. Escrow, fulfillment, the whole flow.
Phase 3. A homomorphic pricing layer for agent transactions — merchants set policy, agents query, no one sees the underlying numbers. Years out, not weeks.
The phrases below are tempting and we've seen others use them. We won't, until they're true.