Short answer: TronSave publishes live TRON energy and bandwidth rental prices as a public JSON file at https://tronsave.io/market/price-index.json. You don’t need an API key or an account. It is refreshed at most every 10 minutes and lists the price in sun per unit for six energy amounts × nine durations, the network burn rate, and what one USDT transfer costs burned vs rented. On November 16, 2026 (UTC) it showed 6.43 TRX to burn for one USDT transfer and 4.32 TRX to rent the energy for one hour. For an exact quote on your own amount, call the free estimate-buy-resource endpoint (also no key). Both are shown below with working code.
If you only want to look at today’s numbers, open the human-readable TronSave energy price index page. This guide is for bots, spreadsheets, dashboards and alerts that need the same numbers in a machine-readable form.
What is in the TronSave price index JSON?
One request returns everything. These are the top-level fields (format version: 2, as of November 2026):
| Field | What it holds | Example (Nov 16, 2026) |
|---|---|---|
updatedAt | When the prices were read from the market (ISO time, UTC) | 2026-11-16T22:59:27Z |
burn | Network burn rate when you have no energy or bandwidth | 100 sun per energy, 1,000 sun per bandwidth (as of November 2026) |
usdtTransfer | Cost of one USDT (TRC-20) transfer: energy used, TRX burned, 1-hour rental cost, 30-day rental cost per daily transfer, and the first-time-recipient case | 64,285 energy; burn 6.43 TRX; rent 1h 4.32 TRX; 30d 2.62 TRX per transfer; new holder 130,285 energy / 13.03 TRX burned (as of November 2026) |
packages | Ready-made TRX totals for 65,000 and 131,000 energy at 1h, 1d, 3d and 30d | 65,000 energy for 1h = 4.37 TRX |
energy | The price grid: durations, amounts and a prices matrix in sun per unit | see the table below |
bandwidth | The same grid for bandwidth (15m, 1d, 3d, 15d × 1,000–50,000) | 5,000 bandwidth for 1d = 784 sun per unit per day (as of November 2026) |
marketOverview | Seller APY for energy and bandwidth, plus available and total resources on the market | energy APY 18.82% |
The file sends Access-Control-Allow-Origin: * and Cache-Control: max-age=600, so a web page can fetch it straight from the browser, and there is no point polling more often than every 10 minutes.
How do you read the price grid?
energy.prices[row][column] is the best price the TronSave market could fill at that moment, in sun per energy unit. Rows follow energy.amounts, columns follow energy.durations. One rule matters more than any other:
- Under 1 day (15m, 1h, 3h), the price covers the whole rental: total sun = amount × price.
- From 1 day up, the price is per day: total sun = amount × price × days.
Divide by 1,000,000 to get TRX. Here is the energy grid as it stood on November 16, 2026 (UTC). These numbers move with supply and demand, so read them from the file, not from this page:
| Energy amount | 15m | 1h | 3h | 1d | 3d | 7d | 30d |
|---|---|---|---|---|---|---|---|
| 64,000 | 65 | 67.25 | 69.75 | 86.5 | 43 | 42.25 | 40.75 |
| 100,000 | 65 | 67.25 | 69.75 | 86.5 | 40 | 39.25 | 37.75 |
| 1,000,000 | 60 | 62.25 | 64.5 | 80 | 39.25 | 38.25 | 37 |
| 5,000,000 | 58.5 | 60.5 | 62.75 | 78 | 38.5 | 37.75 | 36.25 |
| 100,000,000 | 55.25 | 57.25 | 59.25 | 73.5 | 37.25 | 36.5 | 36 |
Worked examples with those prices (as of November 2026):
- 65,000 energy for 1 hour (one USDT transfer): 65,000 × 67.25 = 4,371,250 sun = 4.37 TRX, vs about 6.43 TRX burned (as of November 2026).
- 65,000 energy for 30 days (one transfer a day, because delegated energy refills over 24 hours): 65,000 × 40.75 × 30 = 79.46 TRX, about 2.65 TRX per transfer (as of November 2026).
- 1,000,000 energy for 3 days: 1,000,000 × 39.25 × 3 = 117.75 TRX (as of November 2026).
Why does 1 day cost more per day than 3 days? A one-day rental is priced as a short rental, while longer rentals compete for a seller’s steady, multi-day supply. The TRON energy price guide explains what moves these prices, and the monthly TRON energy price report tracks how they changed over time.
How do you fetch live TRON energy prices? Step by step
- Request the file. A plain GET, no headers needed except a User-Agent. Some default library user agents (for example Python’s built-in
urllib) get a 403 from the site’s bot protection, so set your own, such asmy-price-bot/1.0.curlandrequestswork as they are (tested November 2026). - Check
updatedAt. If it is more than about 30 minutes old, treat the numbers as stale and don’t act on them automatically. - Pick the row and column. Use the largest listed amount that is not above yours, and the duration you need.
- Apply the unit rule (whole rental under 1 day, per day from 1 day up) and convert sun to TRX.
- Cache it for 10 minutes. One request per 10 minutes is all you need, however many users or cells read the price.
curl
curl -s https://tronsave.io/market/price-index.json | jq '.usdtTransfer'
Python (standard library only)
import json, urllib.request
INDEX = "https://tronsave.io/market/price-index.json"
SUB_DAY = {"15m", "1h", "3h"} # price covers the whole rental
DAYS = {"1d": 1, "3d": 3, "7d": 7, "10d": 10, "15d": 15, "30d": 30}
def rent_cost_trx(amount, duration, data):
e = data["energy"]
col = e["durations"].index(duration)
# use the largest listed amount tier that is not above your amount
row = max(i for i, a in enumerate(e["amounts"]) if a <= max(amount, e["amounts"][0]))
sun_per_unit = e["prices"][row][col]
days = 1 if duration in SUB_DAY else DAYS[duration]
return amount * sun_per_unit * days / 1_000_000
req = urllib.request.Request(INDEX, headers={"User-Agent": "my-price-bot/1.0"})
with urllib.request.urlopen(req, timeout=10) as r:
data = json.load(r)
print("as of", data["updatedAt"])
print("burn one USDT transfer:", data["usdtTransfer"]["burnTrx"], "TRX")
print("rent 65,000 energy for 1h:", round(rent_cost_trx(65_000, "1h", data), 2), "TRX")
JavaScript (Node 18+ or the browser)
const res = await fetch("https://tronsave.io/market/price-index.json");
const d = await res.json();
const { oneOff, burnTrx } = d.usdtTransfer;
const saving = 1 - oneOff.rentTrx / burnTrx;
console.log(`${d.updatedAt}: burn ${burnTrx} TRX, rent ${oneOff.rentTrx} TRX (${Math.round(saving * 100)}% less)`);
Both scripts ran against the live file on November 16, 2026 and printed 6.4285 TRX burned vs 4.3232 TRX rented (33% less) for one USDT transfer.
Google Sheets
Sheets’ IMPORTDATA doesn’t parse JSON, so add a tiny custom function under Extensions → Apps Script, then type =TRON_ENERGY_PRICE("1h") in a cell:
function TRON_ENERGY_PRICE(duration) {
const url = "https://tronsave.io/market/price-index.json";
const d = JSON.parse(UrlFetchApp.fetch(url).getContentText());
const col = d.energy.durations.indexOf(duration || "1h");
return d.energy.prices[0][col]; // sun per energy, smallest amount tier
}
Price index or a live quote: which should you use?
The index is a snapshot of the best prices on a fixed grid. When you are about to buy a specific amount, ask for a quote instead. Both are free and need no API key (as of November 2026):
| Source | Best for | Notes |
|---|---|---|
| price-index.json | Dashboards, alerts, sheets, “burn or rent?” checks | Fixed amounts and durations, refreshed at most every 10 minutes |
POST https://api.tronsave.io/v2/estimate-buy-resource | The exact price for your amount and duration right before buying | Returns unitPrice, estimateTrx (in sun) and availableResource; limit 15 requests per second |
TronSave MCP tool tronsave_get_resource_price | Asking an AI assistant for the price in plain language | Read-only, no login; see the TronSave MCP server guide |
A quote for exactly 130,285 energy (a USDT transfer to a never-held address) for one hour:
curl -s -X POST https://api.tronsave.io/v2/estimate-buy-resource \
-H 'Content-Type: application/json' \
-d '{"resourceType":"ENERGY","resourceAmount":130285,"durationSec":3600,"unitPrice":"MEDIUM"}'
On November 16, 2026 a 130,000-energy one-hour quote returned unitPrice 67.25 and estimateTrx 8,742,500 sun, about 8.74 TRX vs about 13 TRX burned. To actually place the order from code, follow the TronSave REST API v2 guide.
What can you build with it?
- A “burn or rent?” check before each payout: if
usdtTransfer.oneOff.rentTrxis clearly belowburnTrx, rent first. On November 16, 2026 that was 33% less for a one-hour rental and 59% less per transfer on a 30-day rental (TronSave’s savings go up to 80%). - A price alert for a Telegram or Slack channel when the 1h price for 64,000 energy drops below a level you choose.
- A budget sheet that multiplies your monthly transfer count by the 30d per-transfer cost.
- A fee line in your own wallet or checkout UI that shows users what a transfer costs right now, with a link to rent the energy.
When the numbers say rent, buy on the TronSave Market (connect TronLink or another TRON wallet, paste the receiver, pay in TRX) or automate it with the API. The guide to renting TRON energy walks through the website flow.
FAQ
Do I need a TronSave API key to get energy prices?
No. The price index JSON and the estimate-buy-resource quote endpoint are both public (as of November 2026). You need an API key only to buy from a TronSave internal balance.
How often is the price index updated?
At most every 10 minutes. Always read updatedAt rather than assuming the file is current.
Is the index price the price I will pay?
It is the best price the market could fill when the file was built, for that amount tier and duration. Prices can move before you buy, and a large order may fill at several prices, so take a fresh quote (or set a maximum price) when you order.
What unit are the prices in?
Sun per unit of energy or bandwidth (1 TRX = 1,000,000 sun). Under one day the price covers the whole rental; from one day up it is charged per day.
Does it include bandwidth prices?
Yes, under bandwidth, for 15m, 1d, 3d and 15d at 1,000 to 50,000 units. On November 16, 2026, 5,000 bandwidth cost 784 sun per unit for one day, against 1,000 sun per unit burned.
Can I show these prices on my own website?
Technically yes: the file allows cross-origin requests, so a browser script can read it directly. Cache it, show updatedAt next to the numbers, and say where they come from.
Is there a testnet version?
The price index covers mainnet only. For quotes on the Nile testnet, call the same estimate-buy-resource endpoint on https://api-dev.tronsave.io; see the Nile testnet guide for free test TRX.
Bottom line
For live TRON energy prices in code, read https://tronsave.io/market/price-index.json: no key, CORS-enabled, refreshed at most every 10 minutes, with the USDT transfer cost already worked out. Use it to decide when to rent, and use a live quote right before you buy.
