Rent TRON energy for USDT transfers

We rent TRON energy per unit for a fixed window and delegate it to the address you name.

Off-peakuntil 11:00
1h energy20 SUN
65k · 1h1.30 TRX

A TRC-20 transfer consumes energy. Without it, the sender burns TRX at the network's fee rate; with it, the transfer costs the rental price and nothing more.

You never send a private key and you never sign a transaction to receive energy — delegation is initiated by us, to your address, and moves nothing out of your wallet. Pay from a prepaid balance, or send a direct transfer to a published address and skip the account entirely.

Open the dashboard Buy from your backend →

Buy energy

1Receiver address

Paste a TRON address, or several — one per line.

2How much

energy

Total for 65,000 energy · 1 h

~~6.50 TRX~~ if you burn it SAVE 80%

1.30 TRX

Your wallet is asked only when you press the button.

Send TRX to the address for the window you want. No account, no signature, no wallet extension.

Rental window

How much energy

I send

TRX

I will receive

energy

20 SUN per energy in the 1h window — the price follows the window and the time of day.

Rules

Energy is counted in whole 1,000-unit steps. The price is the one in force when your transfer arrives.

Before you send

Two identical transfers within ten seconds are two orders, not one.
To rent energy for another address, put that address in the memo. Leave the memo empty and the energy goes to the address you paid from.

Payment address

…

The address is the rental window: each window has its own, so the transfer carries no term parameters. Switch the window and the address changes.

To rent energy for another address, put that address in the memo.

Ready to fill: ✓ 65,000 energy

Your agent reads /llms.txt and the OpenAPI contract and does the integration.

Read prices without a key
Prices and estimates answer an anonymous GET.
Place a signed order
HMAC-signed and idempotent; energy lands on the address in seconds.
Get the webhook
Every state change arrives signed. Rehearse on the Nile testnet first, on its own host and keys.

Connect with MCP

API docs →

API reference openapi.yaml

Four ways to buy

Route	What it needs	Time to first order	Price
Direct transfer	None — send TRX to a published address	Seconds	3.00 TRX per 65,000 energy, flat
Dashboard quick buy	Address challenge, then a deposit	Under two minutes	The published grid
REST API	An API key and a funded balance	One request	The published grid
MCP server / agent	The same API key	One tool call	The published grid

What you are actually buying

Delegated, not transferred

We call DelegateResource against the address you give us. Nothing leaves your wallet, no allowance is approved, no signature is required from you to receive energy.

Verified on chain, not claimed

An order reaches `confirmed` only after we read the receiver's energy limit on chain. A provider saying it delivered is not evidence.

Idempotent by design

Every order carries a `client_order_id`. Retry the identical call after a timeout and you get the original order back, never a second purchase.

One price, published

The grid on this site is the grid the API quotes. Seven day-part windows, shown in your own time zone with UTC beside them, and every window sits at or above the live market reference.

Tiers

Tier	Rental window	Amount bounds (energy)	Sellable
5m	5 minutes	32,000 – 1,000,000	Yes
1h	1 hour	32,000 – 5,000,000	Yes
1d	1 day	65,000 – 10,000,000	Yes
3d	3 days	65,000 – 10,000,000	Not in phase 1
30d	30 days	1,000,000 – 100,000,000	Not in phase 1

Amounts round up to 1,000 units. Above the maximum, the order becomes a reserved-capacity conversation rather than a failed request. See the price grid for what each tier costs in the current window.

From your backend

Two calls: GET /v1/estimate for the price, POST /v1/orders with a client_order_id to place it. The runnable examples in five languages live on the API page and in the docs.

Retrying an order with the same client_order_id returns the original order. A timeout is never a reason to spend twice.

Rehearse on Nile first: api-nile.tenergy.me, separate keys and a separate ledger. It is not identical to mainnet — one provider instead of the full cascade, a fixed price table, and shorter lock and unfreeze periods.

FAQ

Do you ever need my private key or seed phrase?

No, and no feature we have planned will. Energy is delegated to a public address you name; nothing leaves the wallet and no allowance is approved. Anything that asks for a key while renting energy is an attack.

How fast does the energy arrive?

An order runs created → paid → allocating → delegated → confirmed → active. It reaches confirmed only once we have read the receiver's energy limit on chain — a provider's claim is not evidence.

What happens if only part of the order is delivered?

Partial delivery is a field, not a state: the order carries partial: true and delivered_amount, runs through confirmed and active like any other, and the difference is refunded pro rata.

Can I retry a request that timed out?

Yes. Send your own client_order_id on every order. Retrying the identical call returns the original order rather than creating a second one.

Is there a testnet?

Nile, on api-nile.tenergy.me, with separate keys, a separate account and a separate ledger. It is for rehearsing the API shape, not for proving behaviour: one provider instead of the full cascade, a fixed price table, a small fixed inventory, and shorter lock and unfreeze periods.

Do I need an account to buy?

For the API, yes — an account is created by signing a challenge with an address you control, it can create API keys straight away, and orders are paid from its balance once a deposit confirms. A direct transfer to a published address buys energy with no account at all, at the direct-transfer price.