The Payment Rail for AI Agents on TRON
Send USDT. Receive payments. Pay for APIs.
Your agent never touches gas, bandwidth, or keys.
x402 Facilitator on TRON
The x402 machine-to-machine payment standard (Coinbase + Cloudflare) now works on TRON. Three schemes (exact, exact_permit, exact_gasfree), three stablecoins (USDT, USDC, USDD). Any API server accepts payments with one line:
facilitator: "https://x402.merx.exchange"Built for Agents. Not Humans.
Every Protocol Supported
MCP (Anthropic), A2A (Google), ACP (BeeAI). Connect from Claude, LangChain, CrewAI, Vertex AI, AutoGen, BeeAI — zero configuration.
All TRC20 Tokens
USDT, USDC, USDD, and every TRC20 token. Smart send automatically estimates energy + bandwidth and purchases only what’s needed.
Full Payment Stack
Send, receive, watch addresses, create invoices, and settle x402 API payments. Track transaction status through webhooks; confirmation time depends on the network.
One SDK. All of TRON.
Your agent calls three methods. MERX handles the rest.
Register
Add your TRON address. MERX monitors it 24/7.
Call
Use send(), receive(), watch(), or invoice(). Any TRC20 token.
Done
PowerSun supplies the energy. MERX submits the transaction and reports its status through webhooks.
import { MerxClient } from 'merx-sdk'
const merx = new MerxClient({ apiKey: 'sk_live_...' })
// Send USDT — agent never touches energy
await merx.agent.send({
to: 'TRecipientAddress',
token: 'USDT',
amount: '100'
})
// Receive payment notifications through a webhook
const payment = await merx.agent.receive({
token: 'USDT',
webhook: 'https://your-agent/callback'
})Every Agent Framework. One Platform.
The only TRON infrastructure accessible from all three major agent protocols.
Model Context Protocol (Anthropic)
60 tools / 30 prompts / 21 resources
Claude Desktop, Cursor, Windsurf, any MCP client
https://merx.exchange/mcp/sseMCP Server Details →Listed on: Glama · Smithery · MCP Registry
Agent-to-Agent (Google)
8 skills / SSE streaming / task history
LangChain, CrewAI, Vertex AI, AutoGen, Mastra
https://merx.exchange/.well-known/agent.jsonA2A Integration →Listed on: awesome-a2a · a2aregistry.in
Agent Communication Protocol (BeeAI)
8 capabilities / run-based execution
BeeAI, IBM watsonx, ACP frameworks
https://merx.exchange/.well-known/agent-manifest.jsonACP Integration →Automatic Resource Management
When your agent calls send(), MERX handles all of this invisibly:
Comparable quotes covering 65,000 energy for at least 1h, on an activated address. Resource rental only; these are observed quotes, not completed sales. PowerSun fulfils MERX orders. Comparison methodology · Buy energy directly →
Natural Language → On-Chain Automation
"Keep 500,000 energy on my wallet. Buy when price drops below 55 SUN. Max 200 TRX per week."
├─ trigger: price < 55 SUN ├─ amount: 500,000 energy ├─ budget: 200 TRX/week └─ expires: 30 days
Powered by Claude Sonnet 4. Available via MCP tool, A2A skill, and REST API.
Frequently asked questions
- What is TRON energy and why do I need it?
- TRON energy is consumed by smart contract execution, including USDT transfers. The amount depends on the contract and transaction. If available resources are insufficient, the network burns TRX. Renting energy can reduce that cost; the saving depends on the current quote and resources required.
- How does MERX use market prices?
- MERX compares quotes from monitored energy markets to inform its pricing. Quotes can have different amounts, durations, fees and update times. Review the order preview for the price and conditions that apply to your order.
- Who fulfils MERX energy orders?
- PowerSun fulfils MERX energy orders. Other providers are monitored for price comparison and do not receive these orders. MERX and PowerSun share ownership; market comparisons should be read with that relationship in mind.
- What is the commission?
- MERX adds no platform commission to energy orders. The order preview shows the quoted energy cost and any applicable address activation charge. Other services and blockchain operations can have their own fees.
- How fast is delivery?
- Delivery depends on capacity, transaction inclusion and confirmation. A broadcast transaction is not yet a confirmed delegation. Track the order status and transaction references instead of relying on a fixed delivery-time promise.
- Is there an API?
- Yes. MERX provides a REST API, JavaScript and Python SDKs, and an MCP server. One MERX integration provides price comparisons and access to orders fulfilled by PowerSun.
- What happens if an order needs review?
- MERX reconciles confirmed delivery and any address activation before finalizing charges or releasing the unused reserve. An uncertain transaction is reviewed so that an already delivered service is not sent twice.