If you want a script that rents energy the moment a balance runs low, you need a platform that answers HTTP. Eight of the twenty-two platforms on the board are tagged as offering a REST API; this page covers five of them — iTRX, Tronex Energy, MeFree, Feee.io and Tronify. Everything below about how they authenticate comes from the code we run against them every 15 minutes to keep the board fed. Where we have not integrated against a platform's API, we say so rather than describe one.

What we actually know about each one

iTRX — signed requests

Our client sends an API-KEY header alongside a TIMESTAMP and a SIGNATURE, where the signature is an HMAC-SHA256 of the timestamp and the sorted JSON body under an API secret. That is the strongest of the schemes here and the one to copy if you are writing something that will run unattended. iTRX quotes us 1 hour, 1 day and 3 days directly; there is no 15-minute window. On the board right now: 2.27 TRX for 65k/1h.

Tronex Energy — one header

A single X-API-KEY header on a JSON POST to /api/v1/precountOrder. It is the simplest of the five to get working — and, right now, the one that isn't working for us: the endpoint is returning no numeric prices in the current scan, so the board carries no Tronex quote at all. Check the platform directly before you build against it.

Feee.io — API key

Plain key-based auth: one key, no signing, no timestamp to get wrong. Their quotes sit at the expensive end of the board — 5.30 TRX for 65k/1h — which is the trade you are making for the simplest possible integration on a platform that has stayed up for us.

Tronify — REST, with a catch worth knowing

Tronify's queryPreorderInfo endpoint does not quote the energy you asked for. It adds a fixed package on top: ask for 65,000 and the order comes back as 129,400; ask for 131,000 and it comes back as 195,400 — a constant offset of 64,400 energy in every response we have measured. The fee is exactly linear in the energy actually quoted, so the correction is arithmetic: multiply the returned price by the energy you wanted over the energy you were quoted. Skip that step and you will conclude Tronify is about twice as expensive as it is. Corrected, it quotes 4.75 TRX for 65k/1h.

Its pledgeConfig endpoint also publishes the SUN rates behind those quotes, which is the honest way to check any of this yourself: at the published hourly rate of 73 SUN, 65,000 × 73 ÷ 1,000,000 = 4.745 TRX — exactly the figure above.

MeFree — a page, not an endpoint

MeFree carries the API tag on our compare page, but our own price does not come from an endpoint: they print a unit price as a sentence in the order form — 3 TRX per 65,000 energy for one hour — and we read that and multiply. We have never integrated against a MeFree API, so we are not going to describe one. Board price: 3.00 TRX.

The Python wrapper

The shape of it is unexciting, which is rather the point — ask everyone, sort, buy:

def rent_cheapest_energy(amount=65000, duration=3600):
    platforms = [itrx, tronex, mefree, feee, tronify]
    quotes = []
    for p in platforms:
        try:
            quotes.append((p.get_price(amount, duration), p))
        except Exception:
            pass          # a platform that is down is not an error
    quotes.sort()
    return quotes[0][1].rent(amount, duration)

Two things worth building in from the start. Treat a platform that fails as absent rather than fatal — on a given scan at least one of ours is usually down. And never compare a price you derived against one you were quoted: the board marks derived cells with “≈” for exactly that reason.

API vs Telegram bots vs dApps

If you're automating, an API is non-negotiable. Several platforms we track sell through a Telegram bot instead — FeeSaver and re:Fee among them — which you can drive over MTProto, but it is fragile. Others, including Brutus, JustLend DAO and Ergon, are dApps that expect a browser and a connected wallet. Open the Compare tool and filter by "API" for the current list.