FAQ
General
What is AutoEnergy in one sentence?
You connect a TRON address and TRONAgg keeps Energy delegated to it, so the address's USDT/TRC-20 transfers spend Energy instead of burning TRX — fully managed, billed from your TRONAgg balance.
How is it different from the Energy-Free Node?
Both stop transfers from burning TRX, but the model differs:
- AutoEnergy is a per-address subscription. You connect an address; TRONAgg keeps Energy delegated to it in the background. Nothing changes in the sending wallet or its node URL.
- Energy-Free Node is a node URL you point a wallet at; it buys energy per transaction as they pass through.
Pick AutoEnergy when you have a known address (or a few) you want kept Energy-ready hands-off. Pick the Energy-Free Node when you'd rather route a wallet's traffic through a node.
Pricing
What does it cost?
AutoEnergy bills your TRONAgg balance for three things:
| Charge | When |
|---|---|
| Activation | One-time, on subscribe and on each reactivate |
| Daily subscription | Each day the subscription is active |
| Per-transfer | Per transfer, priced by Energy class (standard 65k vs heavy 131k) |
Every amount is set by the (admin-configurable) plan — read the current values from GET /pricing or the workspace. Either way, it's a fraction of what the network would otherwise burn in TRX on each transfer.
How much do I need to subscribe?
Your balance must cover the entry threshold at subscribe time: activation + one daily fee + one 131k transfer. That's a guard so the subscription can operate; only the activation fee is charged up front. Check the current amounts via GET /pricing.
What happens if my balance runs low?
If your balance can no longer cover a due charge, the subscription auto-closes with close_reason: insufficient_balance. Top up and reactivate it.
Lifecycle
When does a subscription close on its own?
For any of these reasons (exposed as close_reason): idle (no activity within your idle_hours window), quota (reached quota_max_tx), expired (passed expire_at), insufficient_balance, daily_cap (an internal safety cap), plus manual and admin closes. See auto-close triggers.
Reactivate vs delete — what's the difference?
- Reactivate re-opens a closed subscription on the same address: recharges the activation fee, resets counters, resumes delegation.
- Delete soft-removes a closed subscription from your list (history kept) and frees the address to be added again as a fresh subscription.
Only a closed subscription can be reactivated or deleted. A live one must be closed first.
Can I run two subscriptions on the same address?
No. An address may hold only one live subscription. A second attempt returns 409 address_busy. If a closed subscription still exists on that address, subscribing returns 409 address_exists — reactivate or delete it first.
Can I change the idle timeout, cap, or expiry later?
Yes, any time, via PATCH /subscriptions/{address} or the workspace. Omitted fields stay unchanged; sending null clears the cap or expiry.
Billing & usage
What am I charged at activation?
Only the activation fee — it covers parking the standing ~131,000 Energy on your address. Per-transfer charges start with your actual transfers: each one is billed exactly once, shortly after it confirms on-chain. See the delegation cycle.
Where do I see what I was charged?
The billing feed lists every charge — activation (autoenergy_activate), daily (autoenergy_daily), and per-transfer (autoenergy_unit) — with amounts and the linked tx id. The usage feed lists the transfer events themselves.
API
Which key do I use?
The same X-API-Key as the rest of the programmatic API. AutoEnergy lives under /api/v1/autoenergy.
Is subscribe idempotent?
Effectively yes on the active address: because only one live subscription per address is allowed, a repeat call returns 409 address_busy rather than creating a duplicate — no idempotency key needed.
Can I manage another user's subscription with my key?
No. Every route is scoped to your account. An address you don't own returns 404 not_found (existence is never leaked as a 403).