USDT transfer cost (public, no key)
Public estimate of a USDT transfer cost: analysis of both addresses, the energy and bandwidth required, and a comparison of burning versus renting. Neither a key nor a whitelisted IP is required.
The rate limit is very low — 1 request per second and 60 per minute, and it is shared. If your application sits behind Cloudflare or another proxy, the limit is effectively shared between every client reaching us through the same edge, so you may hit 429 well before 60 requests a minute. For anything beyond occasional calls use POST /usdt/analyze — it allows 50 requests per second per key.
The addresses are passed in the path, separated by an ampersand.
About client timeouts. The calculator queries TRON nodes live, so under load a single call can take several seconds: set a timeout of at least 15 seconds, better 30 — the usual 10 is too short. On 429 honour Retry-After with a little jitter, on 5xx retry no more than 2–3 times with exponential backoff, and cache the result for 30–60 seconds per address pair.
Every response carries the debug headers X-Request-ID, X-Process-Time and X-Kong-Request-Id — quote them verbatim when contacting support.
Parameters
Path Parameters
Sender address.
"TQn9Y2khEsLJW1ChVWFMSMeRDow5KcbLSE""^T[1-9A-HJ-NP-Za-km-z]{33}$"Receiver address. Must differ from the sender.
"TQn9Y2khEsLJW1ChVWFMSMeRDow5KcbLSE""^T[1-9A-HJ-NP-Za-km-z]{33}$"Responses
Transfer analysis.