Automatic Energy refill on TRON: how it works and who actually needs it
Auto-refill keeps Energy on an address: whenever it drops below a threshold you set, a new portion is delegated and paid from your balance. It is built for hot wallets of services that send USDT at any hour: DEX and payment services, withdrawal wallets and unpredictable payouts. If you send a few transfers a month, or pay out in a batch on a schedule, one-time Energy bought right before is cheaper: about 1.24 TRX per transfer against roughly 24.96 TRX a day for an address kept topped up.What automatic refill is
How it works, and what the service can see
Your own TRON address, how much Energy to add each time, and the threshold below which to add it. No private key or seed phrase is involved.
Energy on the addressThe mark is the threshold of the rule.
Auto-refill against one-time Energy
| One-time Energy | Auto-refill | |
|---|---|---|
| When you pay | Once, before a transfer | Every time the rule fires, each hour that the address is below the threshold |
| Watching the balance | You check before sending | The service does |
| When nothing is sent | Nothing is charged | Deliveries keep being charged until you stop the rule |
| Fits | A few transfers a month, or a scheduled batch | A hot wallet that sends at any hour |
When auto-refill pays off and when it is an overpayment
How many USDT transfers a month do you send?
5 a monthHow much Energy one USDT transfer takes
If the transfer has already failed
Look at your address on tronscan.org: the Energy figure in Resources is what it has right now.
Order Energy for the address you send from, not the recipient’s, in the amount this one transfer needs.
Send the USDT again once the Energy shows on the address.
Open the transaction on TronScan and check that the status is SUCCESS.
Typical setups
A DEX or swap hot wallet
Pays out swaps at any hour, often several close together. Add 650,000 when below 325,000: the threshold sits at half the portion, so a burst of about ten transfers never starts on an empty address.Withdrawals of a payment service
Single withdrawals at unpredictable moments. Add 131,000 when below 65,000: about two transfers at once, and a new portion as soon as the Energy drops under what one transfer needs.Not this: a payout batch once a day
The address would be charged for the hours in between. Order Energy once right before the batch instead.Limits, and how much to keep on the balance
Each delivery is 65,000 to 5,000,000 Energy and lasts one hour; the threshold can be anything from 0 to 5,000,000. An address can have one auto-refill rule.The balance has to cover the next delivery of every running rule together: 2.1 TRX for the default one, or the dashboard refuses to start it. A rule can deliver up to 24 times a day, so for a hot wallet that nobody watches we suggest keeping a day of deliveries in reserve: about 50.3 TRX at this size. That is our advice, not a rule of the service. The low-balance alert below warns you before a rule pauses.
Start auto-refill
What happens next
Enter the address, how much Energy to add each time and the threshold.
Create an account or sign in. The values are kept for you.
Confirm in the dashboard and top up the balance. Only then does the rule start.
What it looks like in the dashboard
Setting up auto-refill with GetGas
Sign up and top up your balance. The balance has to cover the next delivery of all your running rules together.
In the dashboard open Buy Energy, “New automation”, and choose Auto-refill.
Enter the address, how much to add each time and the threshold (“When below”). The form suggests 131,000 and 65,000.
Start it. Pause or remove the rule under Automations whenever you want; if the balance runs out, the newest rules pause by themselves and resume after you top up.
How to check that the Energy arrived
From code, and an alert before a rule pauses
A service can create, pause and remove these rules from code with an API key, and read every delivery in the same account. To hear about a low balance before a rule pauses, set a threshold under API & Keys → Webhook → Low balance alert in the dashboard. When a charge takes the balance below it, a signed balance.low event is sent to your webhook, and again every hour until you top up. It is a webhook, not an e-mail, so it needs a URL on your side.
FAQ
Questions about auto-refill
How do I choose the threshold?
Set it at least at what one transfer needs: 65,000 Energy, or 131,000 if your recipients are often new to USDT. A threshold below that lets a transfer start on an address that cannot finish it.
Is unused Energy lost?
Yes. Energy is delegated for a period, an hour for each auto-refill delivery, and when it ends it goes back whether or not you used it. You pay for the delivery, not for the transfers.
Can I turn auto-refill off, and is anything returned?
You can pause or remove the rule at any time in the dashboard under Automations. Deliveries already made are charged and are not refunded; nothing further is charged once it is stopped.
Do I still need TRX on the address?
For the Energy, no. A transfer also uses about 345 Bandwidth, and every address gets 600 free per day; past that a little TRX is burned. The guide on sending USDT with no TRX in the wallet covers it.
Is Energy enough, or is Bandwidth needed too?
Both are used by every transfer. Energy is the large part; Bandwidth is small and mostly covered by the free daily allowance (600, read on September 21, 2026).
What if the refill has not happened by the time I send?
Then the transfer runs without enough Energy and the network burns TRX for the rest, or fails if there is none. Auto-refill reacts to the balance; it does not know a transfer is coming. For a transfer you are about to make, order Energy first.
Does this work for a withdrawal from an exchange?
No. Energy has to be on the address that signs the transfer, and on an exchange that address is the exchange’s. Auto-refill and one-time Energy both work when you send from your own wallet.