rocketron
PricingAPISolutionsBlogDocs

TRON Energy for Trading Bots

Keep settlement addresses funded with Energy without a strategy thread babysitting it.

AI AgentsExchangesWalletsPayment ProcessorsTrading BotsdAppsOTC Desks

A bot can't afford a failed transfer mid-strategy

A bot moving USDT across venues on TRON can't afford a failed transfer mid-strategy — but it also shouldn't waste cycles polling Energy balance and issuing manual top-ups between trades.

Auto-refill, set once per address

auto-refill (or smart mode) keeps a bot's address topped up automatically; the bot just trades, and rocketron keeps the resource there.

Threshold-based auto-refill — set once per address
Read-scoped keys for pure monitoring processes, purchase-scoped for the executor
A daily spend limit caps how much a bot's Energy spend can run
REST or MCP — same actions either way, pick what your bot stack already speaks

Set an auto-refill rule

One call, then the bot never has to think about Energy for that address again.

curl -X POST https://rocketron.io/api/v1/automations/auto-refill \
  -H "X-Api-Key: rok_4f9a1c8e2b7d..." \
  -H "Content-Type: application/json" \
  -d '{
    "targetAddress": "TXYZ...4f9a",
    "thresholdVolume": 65000,
    "refillVolume": 131000
  }'

Why bots use this

Set once
Auto-refill runs without another call from your strategy code.
Spend-capped
A daily limit on the key bounds worst-case Energy spend.
Separate keys per process
Monitor with a read key, execute with a purchase key.
~0.3s
Doesn't stall a time-sensitive strategy.

Frequently asked questions

01

02

03

04