USDT transfer cost (authenticated)
The same as the public GET, but authenticated and with a limit of 50 requests per second. Use this method for production.
Two forms of authentication are accepted: the X-API-KEY header (preferred — as in the rest of the API) or an Authorization header carrying Bearer {key} or just the key without a prefix. If both are sent, X-API-KEY wins. The request IP must be in the key's whitelist.
There is no amount field. The calculation gives the cost and resource requirements for a single USDT transfer between two addresses: one TRC-20 transfer consumes about 130,000 energy regardless of the amount. If you need the breakdown for several transfers, multiply the recommended energy by their count on your side.
Authorizations
API key from the dashboard. Some Host Mode endpoints also accept the key as an api_key field in the request body — this is stated in the schema of the particular operation.
Request Body
Responses
Transfer analysis — the same structure as the public method returns.