Host Mode - Continuous Energy Management

Host Mode is an automated energy-management system that keeps a TRON address supplied with energy for USDT (TRC-20) transfers, delegating energy for each cycle and re-delegating automatically after the address consumes it.

Overview

Once an address is in Host Mode, the system delegates energy to it and watches the address for USDT transfers. After a transfer consumes the delegated energy, the energy is reclaimed and a new cycle is delegated automatically — as long as the address has cycles left (or is in infinity mode).

Key Features

• Automatic energy: energy is delegated for each cycle without manual action
• Auto re-delegation: after a USDT transfer consumes energy, the next cycle is delegated automatically
• Cycle system: you pay per delegation cycle
• Infinity mode: continuous operation until you stop it

How It Works

1. Add address: register the address in Host Mode (/apiv2/time/add).
2. Buy cycles: order a fixed number of cycles (/apiv2/time/order) or enable infinity mode (/apiv2/time/infinitystart). This activates the address.
3. Delegation: energy is delegated to the address for the current cycle.
4. Usage: when the address makes a USDT transfer and consumes the energy, the system reclaims it and delegates the next cycle.
5. Completion: when all ordered cycles are used, the address is stopped automatically. In infinity mode it keeps running until you stop it.

Cycles and Pricing

• 1 cycle = 1 delegation: each delegation is 131,000 energy and consumes one cycle.
• Pay as you go: ordering cycles does not charge you upfront. Each cycle is charged at the moment its energy is delegated, so the first charge appears right after the mode is switched on, before your first transfer.
• Cycle price: the first delegation of an activation costs 4 TRX. Every next one costs 2 TRX if your previous transfer consumed 65,000 energy or less, and 4 TRX if it consumed more. An activation is the period that starts when an address with no open orders and no active delegation is switched on. Buying more cycles while it is already running continues the same activation. Stopping the address ends it — switch the address on again and the count starts over, so that first delegation is 4 TRX again. The amount returned when you order cycles is an estimate, not the final total.
• Daily minimum (effective 2026-08-29): if an address spends less than 8 TRX over a UTC calendar day, the difference is charged at the end of that day. Two exceptions: the rule does not apply to an address making 3 or more transfers a day, and it does not apply on the first day if the mode was switched on at 16:00 UTC or later — for such an address it starts from the next day.
• Delegation lifetime: 24 rolling hours from the moment energy is delegated. If no transfer happens within that window, the energy is reclaimed, the next cycle is delegated for the following day and charged at the 4 TRX rate.
• Idle shutdown: after 2 consecutive idle days — two 24-hour cycles closed without a transfer — the mode switches itself off and the open orders are closed.
• An extra transfer inside a paid cycle: a second transfer sent in the seconds before the energy is reclaimed reuses that same energy. It does not start a new cycle and does not reduce your remaining cycles, but it is charged separately at the rate matching what it consumed. Leave about a minute between transfers to avoid it.
• Bandwidth: up to 400 bandwidth is delegated together with the energy if the address is short of it. It is free and already included in the cycle price.
• Infinity mode: cycles are effectively unlimited until you stop the address. Everything above still applies — each delegation is charged as it happens, and the daily minimum and idle shutdown work the same way.

Good Fit For

• Active traders making frequent USDT transfers
• Users who do not stake TRX for their own energy
• Services that need energy available on an address without manual top-ups

Management Endpoints

• Time Add — add an address to Host Mode (and register a callback URL)
• Time Order — buy a specific number of cycles (activates the address)
• Time Infinity Start — enable infinity (unlimited) mode
• Time Stop — stop Host Mode and close open orders
• Time Delete — remove an address from Host Mode
• Time Status — check addresses, modes and cycle counts

Authentication

Every request requires:

1. API key — passed in the JSON body (api_key) or the X-API-KEY header.
2. Whitelisted IP — the request IP must be in the whitelist configured for your API key.

All endpoints return a JSON envelope:

{ "code": 0, "msg": "…", "data": { } }

code = 0 means success; a negative code means an error (see msg).

Callbacks (webhooks)

When you register a callback_url for an address (via /apiv2/time/add), the system notifies your URL each time energy is delegated to that address. The callback carries the delegation hash, the amount charged for the cycle (charged, TRX, always present) and — only when the cycle was born from your transfer — the tariff band of that transfer's energy consumption (energy_used: 65k or 131k, otherwise the parameter is omitted). See Time Add → Callbacks for the exact request format.

Best Practices

1. Verify the address is correct and activated on the TRON network before adding it.
2. Keep enough balance — cycles are charged as they are delegated, not when you order them.
3. Start small with a few cycles before enabling infinity mode.
4. Monitor your addresses, cycle counts and actual spend with the Time Status endpoint.
5. Leave about a minute between transfers from the same address, so the second one does not reuse energy that is already being reclaimed.
6. Stop addresses you are not using — an idle address still costs the daily minimum until it shuts itself off.
7. Protect your API key — never expose it in client-side code; keep your IP whitelist up to date.

Getting Started

1. Obtain an API key and whitelist your server IP.
2. Add the address with /apiv2/time/add.
3. Order cycles with /apiv2/time/order or enable infinity mode with /apiv2/time/infinitystart.
4. Monitor status with /apiv2/time/status.