Questions and answers
What integrators ask before the first order, grouped and answered short. Where an answer belongs to the contract rather than to a habit of ours, the API documentation says the same thing at length.
Energy and pricing
What is TRON energy?
A network resource that pays for smart-contract execution. With enough energy on the sending wallet, a USDT transfer burns almost no TRX.
Why is it cheaper than burning?
Burning prices energy at the protocol rate, ~210 sun per unit — a number that never moves. We source delegated energy in volume and sell it at a fraction of that rate; the price in force right now is on the pricing page.
See all prices →
What if I miss the 4-minute window?
In mode A the charge stands — the energy was delivered, and delivery is what you pay for. In mode B nothing is broadcast once the window has closed, so the position fails and the reservation comes back in full. The window comes with every order — build your flow around it.
Does missing the send window cost the same in both modes?
No. In mode A the energy was delivered, so the charge stands — and so it does in mode C, where there is no transfer to wait for and the position simply expires when the window closes. In mode B we never broadcast once the window has closed: a transfer sent late would meet a wallet the delegated energy has already left, and burn your TRX. The position closes as failed with broadcast_window_missed, the whole reservation comes back, and the energy we bought for it is our loss.
Money and refunds
How do I pay?
Prepaid service credits, denominated in TRX: send TRX to your personal address, spend on services. Prices are fixed at order creation.
Which token can I send to my deposit address?
TRX, and only TRX. USDT sent to a deposit address is not credited automatically: we take no exchange-rate risk and run no conversion service, so it is set aside for a person to look at and crediting it is our decision case by case. Sent the wrong token? Write to us, and do not send more.
How soon can I spend a deposit?
After 3 confirmations — about ten seconds. Your balance is then reported in three parts: the total, the part held against orders in flight, and the part available. An order is created out of the available part, never out of the total.
Can I cancel an order?
Only before procurement starts; after that the answer is order_not_cancelable, because the energy has already been bought. A cancelled order releases its reservation in full and charges nothing.
What about refunds?
Releases are automatic and never need a ticket. The rule is one — energy we did not deliver is not charged, and the reservation comes back to your balance in service credits: a failed delivery, an order cancelled before procurement began, the unspent part of an Auto-refill day. Delivered energy is charged, used or not.
Security and keys
What keys do you need?
None. Mode A never sees your transaction. Mode B takes one you already signed, and we cannot alter a byte of it.
Do you accept a multisig sender?
In mode B, no: the transaction has to carry exactly one owner signature, with Permission_id 0. The key set of a multisig account lives on the chain and changes without our knowledge, so we cannot promise the broadcast would be accepted. In mode A nothing about your signing reaches us — you broadcast the transfer yourself.
What do you store, and for how long?
In mode B your signed transaction is kept encrypted and erased 7 days after the order reaches a final status. Orders, ledger entries and deposits stay: that is accounting, and it is the part we are obliged to keep. Nothing else of yours is here — no private keys, no seed phrases, no custody of your funds.
Integration
Are there limits?
120 orders a minute per key, up to 500 transfers per batch order. Over the limit you get Retry-After, not a silent drop.
What does completed actually mean?
That the energy was delivered — not that your transfer was sent. Delivery is the obligation, so the order closes on it, and in mode A completed can arrive before you have sent anything. Watch for send_before appearing on the order rather than for the word ready: polling every two seconds, you may never see ready at all.
How does idempotency work?
An Idempotency-Key is bound to the raw bytes of the body it arrived with. The same key and a byte-identical body give you the same order back; the same key with a different body is a conflict; a request turned down by validation does not spend the key, so you may repeat it with the same key once the body is fixed. Serialise the body once and resend those exact bytes — another key order or one extra space is a different body.
Can I check an address before paying for anything?
Yes, and it is free. GET /v1/address-check reports what we know about a wallet, and POST /v1/estimate prices up to 500 recipients by the same rules an order would use — including which of them the token contract blacklists. Neither reserves anything and neither charges anything.
Your account
Can a wallet stay topped up by itself?
Yes — an auto-refill rule: an address plus a daily budget. Energy refills after every transfer; the budget is a hard daily ceiling.
What should I set balance.low to?
The number is a setting of your own — balance_low_threshold_trx in PATCH /v1/settings; balance.low is the event it fires. About one day of your turnover is the useful size: the warning then arrives a day before orders start meeting insufficient_balance, instead of arriving in place of the first refusal. Much lower and the event is a notice after the fact; much higher and it is noise. Zero switches it off.
Is there a sandbox, or a minimum volume?
No minimum volume, no subscription and nothing to pay for idle time. There is no sandbox either: the base URL is the live one and it is the only one there is. The reference endpoints, an estimate and a webhook test cost nothing, so most of an integration can be built before a single order exists.