Buy TRON Energy. Stop burning TRX.

Energy is delegated to your address within seconds and expires on its own. Pay from your own wallet, with no account and nothing to submit.

✓ No account — just TronLink ✓ 10 minutes or 1 hour ✓ Non-custodial ✓ Delegated on-chain

Energy amount

Roughly one USDT transfer.

Duration

Receive energy at

The wallet you pay from · send it somewhere else

Order—

Rate—

You pay—

vs. burning TRX instead

—

You would burn about — in network fees.

Checking for TronLink…

No wallet needed to see the price.

How it works

Three steps, and the energy expires on its own.

Pick amount and duration

10 minutes for a quick transfer, or 1 hour if you have several to do.

Pay the exact amount

Confirm in TronLink. The wallet sends the exact amount and signs it — nothing to copy, nothing to get wrong.

Energy arrives

We watch the chain, detect your payment, and delegate. Nothing to submit, and nothing to cancel.

Your orders

Tracked in this browser. Nothing is stored on a server for you.

Order	Energy	Duration	Paid	Status	Transaction
No orders yet.

Use the API

For bots and scripts. Create the account by API call, fund it, then rent energy — no wallet popup per order.

How the API differs from this page

Over the API you fund an account with TRX once, and then spend that balance on rentals. There is no wallet popup and nothing to sign — which is what makes it usable from a server.

Buying

Prepaid

spent from your balance

Auth

X-API-Key

one header, no signature

Settlement

On-chain

energy delegated to you

Your balance is not refundable and cannot be withdrawn. Deposits become prepaid credit that is spendable on energy, and on nothing else. Fund a small amount first.

1 · Get an account

Create one with a single call. You receive two things: a deposit address (yours alone) and an API key. The key is stored only as a hash, so it is shown once and cannot be recovered — keep it in your secret store, because nobody, including the operator, can show it to you again.

# no account needed to sign up — the key comes back in the response
curl -s -X POST https://your-api-host/api/v1/account/signup
# 201 {"api_key":"tek_…","deposit_address":"T…","network":"nile"}

Send TRX to your deposit address to fund it. The amount received becomes your balance, valued in TRX at the moment it is credited. Any amount above zero is credited — there is no minimum top-up, and a small one buys real energy.

2 · Read the prices

No key needed. Charge is energy_units × price_sun_per_unit; SUN is TRX × 1,000,000.

GET /api/v1/products

curl -s https://your-api-host/api/v1/products

{
  "products": [
    {
      "duration_seconds": 600,
      "duration_label": "10 minutes",
      "price_sun_per_unit": "42.000000",
      "price_trx_per_unit": "0.000042",
      "min_units": 32000,
      "free_energy": 76978,
      "energy_per_trx": 73.663468
    }
  ],
  "network": "nile"
}

3 · Check your balance

Send your key in the X-API-Key header on every account call. A key in a URL would end up in logs, so it is not accepted there.

GET /api/v1/account

curl -s https://your-api-host/api/v1/account \
  -H "X-API-Key: $API_KEY"

{
  "deposit_address": "TFfZnVFL3QNUAvnLXbmDF4amGFCgMr4xVu",
  "status": "active",
  "balance_sun": "50000000",
  "balance_trx": "50.000000",
  "rentals": 0,
  "ledger": []
}

4 · Rent energy

This spends your balance and delegates energy to receive_at — any address you name, not only your own. The energy expires by itself at the end of the duration; there is nothing to cancel and nothing to give back.

POST /api/v1/account/rentals

field	required	notes
energy_units	yes	whole number, minimum 32,000
duration_seconds	yes	600 or 3600 — from /products
receive_at	yes	TRON address that receives the energy
idempotency_key	yes	your own unique string, one per order. A retry with the same value replays the original result instead of charging twice, so keep it stable while retrying and use a new one for a new order — generate it (a GUID), never count up by hand.

curl -s -X POST https://your-api-host/api/v1/account/rentals \
  -H "X-API-Key: $API_KEY" \
  -H "content-type: application/json" \
  -d '{
        "energy_units": 65000,
        "duration_seconds": 600,
        "receive_at": "TYwNTbHK7f9yutJ8cfqQXPBi7UDbUA5mFj",
        "idempotency_key": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e"
      }'

{
  "id": 12,
  "status": "delegating",
  "recipient_address": "TYwNTbHK7f9yutJ8cfqQXPBi7UDbUA5mFj",
  "energy_units": 65000,
  "duration_seconds": 600,
  "charged_sun": "2730000",
  "balance_sun": "47270000",
  "replayed": false
}

# ---- the same orders from PowerShell ----
      #
      # RENTAL LENGTH - both options, pick either:
      #     $rent = 600    10 minutes   42 sun per unit    (32,000 units = 1.344 TRX)
      #     $rent = 3600   1 hour       45 sun per unit    (32,000 units = 1.440 TRX)
      #
      # RECIPIENTS - your own addresses, separated by COMMAS. One order each.
      $key   = 'YOUR_API_KEY'
      $Addrs = 'ADDRESS_1', 'ADDRESS_2', 'ADDRESS_3'
      $rent  = 600
      $units = 32000
      $H     = @{ 'X-API-Key' = $key }

      foreach ($a in $Addrs) {
      $b = @{
      energy_units     = $units
      duration_seconds = $rent
      receive_at       = $a
      # a fresh key per order: re-running buys again, it does not replay
      idempotency_key  = [guid]::NewGuid().ToString()
      } | ConvertTo-Json
      try {
      $r = Invoke-RestMethod -Uri 'https://your-api-host/api/v1/account/rentals' `
           -Method Post -Headers $H -ContentType 'application/json' -Body $b
      Write-Host "OK   $a -> $($r.energy_units) units for $(($rent / 60)) min"
      } catch {
      # the API's own words live on ErrorDetails; a plain-string error leaves it empty,
      # so fall back rather than printing a blank reason
      $why = $_.ErrorDetails.Message
      if (-not $why) { $why = $_.Exception.Message }
      if (-not $why) { $why = "HTTP $([int]$_.Exception.Response.StatusCode)" }
      Write-Host "FAIL $a  $why"
      }
      }

A fresh idempotency_key per order is what makes the loop safe to re-run: paste it again and you would buy again, so use your own order reference if you want a retry to replay instead of charge. Orders are queued — the response says delegating and the energy lands a moment later, one recipient at a time.

A retry of the same idempotency_key answers 200 with replayed set to true and the charged_sun unchanged, so a network timeout never costs you twice. Keep the key stable per order — a fresh key on a retry is a second purchase.

TREAT AN UNEXPECTED replayed: true AS YOUR OWN BUG — nothing new was bought. A replay returns the ORIGINAL order: its recipient, its amounts, its charge, and no new energy. So if you send a key you have already used for a different order, you get a cheerful 200 describing the EARLIER purchase and your new recipient receives nothing. It is not an error on the wire and it will not raise an exception, which is exactly why it is worth checking: if you did not expect a replay, the order you thought you placed does not exist. Generate a key per order (a UUID) and a replay will only ever be a retry you deliberately made.

5 · Endpoints and limits

method	path	auth	limit
GET	/api/v1/products	none	—
GET	/api/v1/estimate	none	60/min
GET	/api/v1/account	X-API-Key	60/min
POST	/api/v1/account/rentals	X-API-Key	120/min
GET	/api/v1/orders?payer=<address>	none	120/min
GET	/api/v1/orders/<ref>	none	120/min

/v1/... is an accepted alias for /api/v1/..., so either prefix works.

6 · Errors

Every failure has the same shape: { "error": { "code", "message" } }. Switch on code, not on the message text.

HTTP	code	meaning
401	unauthorized	the X-API-Key header is missing or the key is unknown
400	validation_error	a field is missing or malformed — the message names it
402	insufficient_funds	your prepaid balance does not cover this order. Top up — and the reserve happens before the charge, so a refused order costs you nothing
409	insufficient_liquidity	the pool cannot cover that many units right now; buy less or retry later
429	rate_limited	too many requests for that endpoint — see the per-endpoint limits above; retry shortly

A 409 costs you nothing: the balance is only charged once the energy is reserved, so a request that cannot be filled leaves the balance untouched.

7 · Before you rely on it

Prices move. Read /products before pricing a job; the rate per unit can change.
Rentals expire. Energy returns to the pool when the duration ends. Nothing to unwind.
Addresses must be active on-chain. Energy cannot be delegated to an address that has never received a deposit, so the API refuses one up front instead of taking your money.
The payer wallet is separate. Prepaid credit is bought by sending TRX to your deposit address; it is not tied to whatever wallet you connect on this page.
This deployment is on the same network as the page. Testnet and mainnet are different chains — a key and a balance on one do nothing on the other.

Day (UTC)	Payments	Earned
No sales yet.

Duration	Payments	Energy sold	Earned
No sales yet.

Your account

For API buyers. Prepaid credit, spent on energy.

Make an account

Sign one short message with a TRON wallet and your account is created — deposit address and all. Signing is inert: it moves no funds, spends no balance and grants no spending power. Its only job is to prove the wallet is yours.

Keeping it recoverable costs nothing and is decided now. An account made with a wallet can always be re-keyed by signing again. Create it by API call instead and no wallet is recorded, so a lost key can never be replaced. If you would rather have that, use POST /api/v1/account/signup on the Bots & scripts tab.

Sign in with your API key

This is the key you were issued when your account was created. It is stored only as a hash, so it cannot be recovered or emailed to you — keep it somewhere safe. Your deposit address is not enough to sign in here: it is safe to share and is not treated as a secret.

API key

Lost your key? Or want an account a wallet can recover?

Connect a wallet and sign a short message. Signing moves no funds and spends nothing — it proves the wallet is yours, nothing more. Two things you can then do:

Open a new account whose identity is this wallet. Keep the key safe, but if you ever lose it this wallet can sign for a new one.
Replace a lost or leaked key for an account you opened with this wallet. The old key stops working immediately.

Your wallet is not your deposit address. The wallet is the one you hold and sign with. The deposit address is a separate thing we derive for you to send TRX to — you cannot withdraw from it, and your deposits become prepaid credit spendable on energy only.

Your balance

Prepaid credit. Spendable on energy only — it cannot be withdrawn or refunded.

Balance

—

Account

—

Fund it

Send TRX

to the address below

Your deposit address

Send TRX here to top up. Any amount is credited to this account as prepaid credit once it is confirmed on-chain. This address is yours alone.

Recent activity

Every credit and charge against this account, newest first.

When (UTC)	What	Amount	Balance after	Reference
Sign in to see your activity.

Call the API with your key

Same account and the same balance shown above: anything rented here is charged to that prepaid credit. Send the key in the X-API-Key header — never in the address bar, which lands in logs.

1 · Choose a duration

Two lengths, and the price per unit differs between them. Prices are per duration, so read them from the API rather than assuming the shorter one is cheaper.

curl -s https://your-api-host/api/v1/products

# 600  = 10 minutes   42 sun per unit   32,000 units = 1.344 TRX
# 3600 = 1 hour       45 sun per unit   32,000 units = 1.440 TRX

2 · Read your balance

curl -s https://your-api-host/api/v1/account \
  -H "X-API-Key: tek_your_key_here"

3 · Rent energy — one address

receive_at takes exactly one address. There is no list form and no separator: to serve several wallets, send one request per wallet.

curl -s -X POST https://your-api-host/api/v1/account/rentals \
  -H "X-API-Key: tek_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
        "energy_units": 32000,
        "duration_seconds": 600,
        "receive_at": "TYourReceivingAddress",
        "idempotency_key": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e"
      }'

# Generate a NEW one per order — a UUID is the easy way, and it cannot collide:
#     PowerShell : [guid]::NewGuid().ToString()
#     bash       : uuidgen   (or: cat /proc/sys/kernel/random/uuid)
# Keep the SAME one only while retrying that one order: a retry replays instead of charging twice.

# 201 {"id":12,"status":"delegating","recipient_address":"T...","energy_units":32000,
#      "duration_seconds":600,"charged_sun":"1344000","balance_sun":"...","replayed":false}

4 · Rent energy — many wallets

One order per address, so the loop is the list. This is the same script as the Bots & scripts tab, kept here because it is your account being charged.

# ---- many wallets, one order each ----
#
# LENGTH - both options, pick either:
#     $rent = 600    10 minutes   42 sun per unit   (32,000 units = 1.344 TRX)
#     $rent = 3600   1 hour       45 sun per unit   (32,000 units = 1.440 TRX)
#
# RECIPIENTS - your own addresses, separated by COMMAS. One order each.
$key   = 'tek_your_key_here'
$Addrs = 'ADDRESS_1', 'ADDRESS_2', 'ADDRESS_3'
$rent  = 600
$units = 32000
$H     = @{ 'X-API-Key' = $key }

foreach ($a in $Addrs) {
  $b = @{
    energy_units     = $units
    duration_seconds = $rent
    receive_at       = $a
    # a fresh key per order: re-running buys again, it does not replay
    idempotency_key  = [guid]::NewGuid().ToString()
  } | ConvertTo-Json
  try {
    $r = Invoke-RestMethod -Uri 'https://your-api-host/api/v1/account/rentals' `
         -Method Post -Headers $H -ContentType 'application/json' -Body $b
    Write-Host "OK   $a -> $($r.energy_units) units for $(($rent / 60)) min"
  } catch {
    # the API's own words live on ErrorDetails; a plain-string error leaves it empty,
    # so fall back rather than printing a blank reason
    $why = $_.ErrorDetails.Message
    if (-not $why) { $why = $_.Exception.Message }
    if (-not $why) { $why = "HTTP $([int]$_.Exception.Response.StatusCode)" }
    Write-Host "FAIL $a  $why"
  }
}

5 · Other calls

Call	What it is for
GET /api/v1/products	The durations and the price per unit. No key.
GET /api/v1/account	Balance, rentals and ledger for your key.
POST /api/v1/account/rentals	Spend balance on energy. One address per call.
GET /api/v1/orders?payer=T...	Order status. No key — pass the payer address.
POST /api/v1/account/deposits/claim	Credit a top-up the watcher missed, by txid.

idempotency_key is required on the rental call. Keep it stable per order so a retry replays rather than charging twice, and use a new one for a genuinely new order. If a call ever comes back replayed: true when you did not retry, nothing was bought — a replay returns the original order, so your new recipient got nothing. Treat it as your own bug, not a success.

Buy TRON Energy. Stop burning TRX.

How it works

Pick amount and duration

Pay the exact amount

Energy arrives

Your orders

Use the API

How the API differs from this page

1 · Get an account

2 · Read the prices

3 · Check your balance

4 · Rent energy

5 · Endpoints and limits

6 · Errors

7 · Before you rely on it

Owner — your earnings

Last 30 days

By product

Owner sign-in

Your account

Make an account

Sign in with your API key

Lost your key? Or want an account a wallet can recover?

Your balance

Your deposit address

Recent activity

Call the API with your key

1 · Choose a duration

2 · Read your balance

3 · Rent energy — one address

4 · Rent energy — many wallets

5 · Other calls