Published: October 28, 2026. Status checked against the x402 repository and Coinbase’s facilitator docs on that date.
Short answer: not officially yet. As of October 28, 2026 the TRON binding for x402 is an open proposal (pull request #2076 in the x402 Foundation repository), and Coinbase’s hosted facilitator does not list TRON. When it lands, USDT payments will go through Permit2, and every settlement will cost the facilitator TRON energy.
What is x402?
x402 is an open payment protocol built on the HTTP status code 402 Payment Required. A server answers a request with the price and accepted payment terms; the client, often an AI agent, signs a payment authorization and retries the request with it attached. A facilitator checks the authorization and settles it on-chain, and the server returns the resource.
The point is that an agent can pay per request, without an account, an API key or a card on file. The protocol lives in the x402-foundation/x402 repository, which already has exact payment bindings for EVM chains, Solana, TON, Sui, Aptos, Stellar and others.
Does x402 support TRON?
Here is where things stood on October 28, 2026:
| Piece | Status |
|---|---|
TRON exact binding (spec) |
Proposed in PR #2076, “specs(exact): add TRON binding”. Open, not merged. |
| Coinbase (CDP) hosted facilitator | Supports Base, Polygon, Arbitrum, Monad, World and Solana. TRON is not listed. |
| Contracts the proposal references | Permit2 and an “exact proxy” are deployed and verified on TRON mainnet, Nile and Shasta. |
A spec merge is the first milestone, not the last. Agents also need client libraries and a facilitator that settles on TRON before paying with USDT on TRON becomes routine.
How would an x402 payment in USDT on TRON work?
The proposal defines two ways to authorize a TRC-20 payment:
tip3009: a signedTransferWithAuthorization, TRON’s version of EIP-3009. The token itself must implement it, and TIP-3009 is still a draft.permit2: a signed Permit2 transfer, settled through the exact proxy contract. The proposal names this as the practical path for USDT, which does not implement TIP-3009.
For USDT, the flow would be:
- One-time approval. The payer approves the Permit2 contract to spend their USDT. This is an ordinary on-chain transaction the payer signs and pays for.
- Per-payment signature. For each request, the agent signs a Permit2 authorization off-chain. Signing costs nothing.
- Settlement. The facilitator submits the transaction that moves the USDT and pays its energy and bandwidth.
Networks are identified with CAIP-2 IDs: tron:728126428 for mainnet and tron:3448148188 for the Nile testnet.
Who pays the TRON energy in x402?
Two parties, at two different moments:
| Transaction | Who signs and pays | How often |
|---|---|---|
| Permit2 approval of USDT | The payer | Once per wallet and token |
| Settlement of each payment | The facilitator | Every payment |
The proposal says the facilitator’s account must be activated and “able to cover settlement costs through available Energy/Bandwidth or the network’s TRX payment fallback”, and that pre-staked resources are not mandatory. In plain terms, a facilitator either holds energy or burns TRX at 100 sun per unit on every settlement. The binding does not sponsor the payer’s approval either.
That is the same choice every high-volume TRON sender faces, and the same arithmetic applies. Since a facilitator settles all day, it is the “steady daily activity” case where a multi-day rental works out cheapest per transaction; see how TRON energy rental cost is calculated.
What can an AI agent do on TRON today?
Without x402, an agent can still pay for energy and send USDT on TRON with ordinary signed transactions:
- Get a live price and total for any amount and duration, with no login, from the TronSave MCP server (
tronsave_estimate_buy_resource). - Place an order paid with a TRX transfer that the user signs in their own wallet (
tronsave_create_orderwithpaymentMethod=onchain). - Use the energy for the transfer itself, which needs 64,285 energy for a USDT transfer to a wallet that already holds USDT (details).
Agents find these tools through standard discovery files; see llms.txt and .well-known for AI agents.
What should a builder do while the spec is open?
- Prototype on Nile. The proposal lists Permit2 and exact-proxy addresses for the Nile testnet, so the whole flow can be tested without real funds.
- Measure the energy. Record what the approval and a settlement actually consume on Nile, rather than assuming a plain transfer’s figure.
- Plan the approval step. Payers need TRX or energy for the one-time Permit2 approval, and a brand-new wallet also needs activating first.
- Budget the facilitator side. Multiply settlements per day by the measured energy, then compare burning with renting for that daily amount.
- Keep the network ID configurable. The proposal requires decimal CAIP-2 IDs, so older hexadecimal forms may need migrating.
FAQ
Can I pay with x402 in USDT on TRON today?
Not through the official specification or Coinbase’s facilitator as of October 28, 2026. The TRON binding is still an open proposal.
Does x402 make TRON transactions free?
No. Someone still pays for energy and bandwidth. In x402 the facilitator pays for settlement, and the payer pays for the one-time Permit2 approval.
Why Permit2 and not a plain USDT transfer?
x402 needs a payment the payer can authorize off-chain and someone else can submit. USDT on TRON has no built-in authorization method, so the proposal routes it through Permit2 after a one-time approval.
Will this change how much energy a USDT transfer needs?
A settlement is a contract call through the proxy and Permit2, not a direct transfer, so its energy use will differ from the 64,285 of a plain transfer. Measure it on the Nile testnet before budgeting.
Where do I follow progress?
Watch PR #2076 in the x402-foundation/x402 repository and the CDP network support page.
