Dramatically lower transaction costs on TRON
The scale of the savings may shock you. First results arrive on your live flow, before any integration.
We know TRON resources at the level of every block: how Energy is consumed and recovers, how the network counts Bandwidth, how stake behaves on delegation and reclaim. That knowledge became a precise consumption model for every address.
There is always enough resource — we stay one step ahead. Our services see the consumption of every address block by block and place Energy and Bandwidth in advance: when a transaction goes out, the resource is already on the address. The reserve for bursts is ours.
- Exchange withdrawals
- Merchant payouts
- Mass payouts
- Wallet sweeps
- Contract calls
An AI agent buys TRON resources on its own
One HTTP exchange with USDC on Base: the agent reads the price, pays by x402 and gets the result. The full recipe is in /llms.txt.
- 1.GET https://api.awesomefee.com/v1/search?q=energy — product, price, example
- 2.GET https://api.awesomefee.com/x402/v1/quote?product=energy&amount=65000 — price
- 3.POST https://api.awesomefee.com/x402/v1/tron/energy → 402 with the payment terms
- 4.The same request with PAYMENT-SIGNATURE (USDC on Base) → 200
- 5.Energy is on the address — the transaction goes as usual
The solution is ready. Connecting takes minutes
Integration costs money and hours of your team. We left those hours with you: the services fit into a running system as it is.
Resource on your addresses, always
You name the addresses, we do the rest. Thresholds are recalculated on every block from the consumption history of the address, with a reserve for bursts. The resource arrives before it is needed.
The time a resource stays on the address is on us. Only what was consumed reaches the bill.
To connect: a list of addresses
How Mate works →Resource at the moment of sending
Our node is a full mirror of a TRON node: HTTP, JSON-RPC, gRPC. It provides the sender with the resource and passes the transaction to the network in its original form.
Keys and signatures stay on your side — TRON is built that way. We work with what is public: the address and the resource on it.
To connect: a node address
How Proxy works →Volume for a planned peak
Energy and Bandwidth on any address for a set term, with the price known in advance.
VaultA reward for your stake
The resource of your stake works, the TRX stay on your address.
AI Agents & x402Resource for AI agents
One HTTP exchange: request, USDC payment, executed transaction.
The services are built for exchanges, payment processors and payment systems.
TRON right now
Our index reads every block of the network: how much resource is spent and how much TRX burns right now.
Open the network data →We already know how your address works
We index every block of the network. Enter an address — the analysis is ready at once, from open blockchain data.
The analysis is built on the questions finance and technology directors bring to us:
- How much do we pay for resources?
- The full picture by hour, in TRX.
- How does our stock work?
- How much was bought and how much was consumed.
- Where do TRX burn?
- The hours and addresses where demand outran the stock.
- How much will we save?
- The same flow under our model — in one figure.
You pay for what was consumed
The unit of payment is the resource your address actually consumed from our supply. A transfer consumed Energy — it is on the bill. Everything else is on us.
-
Time on the address is on us
In Mate the resource stays on your address for as long as it takes. You pay for consumption; the waiting time stays on our side.
-
We hold the reserve
The reserve for bursts sits on our side and at our expense.
-
We answer for the result
Every transaction on a serviced address is provided with the resource — that is our contractual obligation.
-
The bill is visible in advance
In watch mode Mate runs on your live flow and shows every operation and the amount before the first payment.
For developers and AI agents
One request puts the resource to work: OpenAPI, x402, llms.txt and SKILL.md. Your code works with TRON resources the way it works with any API.