Skip to main content

Getting started

You need a TRONAgg account. Creating a configuration also needs a balance at or above the activation threshold (10 TRX at the time of writing). It stays on your balance and pays for the Energy of each sale. You can fill in the whole form first: if your balance is short, its last step shows how much to top up.

1. Create a configuration​

  1. Sign in at tronagg.ai/workspace and open Energy Agent → Configurations in the sidebar, or go straight to tronagg.ai/workspace/agent.
  2. Click New configuration.
  3. Choose how you receive payments:
    • Use my address: paste a TRON address you control. Customer TRX goes straight into it.
    • Generate an address: TRONAgg issues a dedicated address whose payments land on your TRONAgg balance. The address is permanent, so it can be paused but never deleted.
  4. Fill in the numbers:
    • Energy per unit: Energy one base payment buys. 65,000 covers one standard USDT transfer.
    • Base payment: your TRX price for one unit, 3 TRX by default. It must cover TRONAgg's highest hourly price for that Energy; the form shows the lowest, current and highest price so you can see your margin.
    • Max units per payment: the most units one payment can order.
    • Title (optional): shown on your pay page, for example your shop or channel name.
  5. Click Create configuration. It starts active straight away.
The New configuration form: where customers pay, Energy per unit, base payment, max units per payment, an optional title, and an estimate of the price and your profit per unit.

See How it works for every validation rule.

2. Share your pay page​

Every configuration has a public pay page: customers pick how much Energy they need, then pay from TronLink in one confirmation or send TRX to your address by hand, with a QR code. From the configuration's row:

  • Copy pay link copies https://tronagg.ai/pay/<id> to share in a channel, group chat, website or wallet guide.
  • Open pay page shows it the way your customers see it.
  • Show QR code gives you a QR to print or post.

You can also share the bare address. The pay page is simply easier to follow, and it tells customers the one thing that matters most: pay from the wallet that needs the Energy, not from an exchange, because Energy goes to the sending address.

A pay page on a phone: the customer picked 2 units, 130,000 Energy for 7.000 TRX, with a Pay with TronLink button, a QR code, the address and copy buttons.

3. Watch your sales​

Each payment appears on the Sales page (Energy Agent → Sales in the sidebar, or View sales above your configurations) with the customer address, the amount, the Energy delivered, what TRONAgg charged and its status. Skipped payments show their reason, and the header shows your total sales, Energy and profit.

The Sales page: every payment with its time, configuration, payer, amount paid, Energy delivered, TRONAgg&#39;s charge, your profit and its status. Skipped payments show their reason.

To be notified as sales happen, turn on the agent.sale and agent.payment_skipped events in Workspace → Notifications, for Telegram or a webhook.

4. Invite other agents​

The referral card on the Energy Agent page links to your referral program. Agents who join through your link earn you commission on the Energy they buy, and your pay page's "Powered by TRONAgg" footer carries your referral code automatically.

Create a configuration via the API​

Everything above is also available under /api/v1/agent, authenticated with your X-API-Key. See Authentication if you don't have a key yet.

curl -X POST https://tronagg.ai/api/v1/agent/configs \
-H "X-API-Key: ta_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"mode": "generated",
"title": "Night Shift Energy",
"energy_per_unit": 65000,
"base_payment_sun": 3000000,
"max_units": 10
}'

A 201 response returns the new configuration, including its address and the public_id of its pay page. See the API reference for every endpoint.

What's next​

  • How it works: skipped payments, automatic pause and resume, and address modes.
  • API reference: endpoints, errors and webhook payloads.
  • FAQ: common questions.