TRON Energy & Bandwidth for dApps
Sponsor your users' transactions without asking them to hold TRX.
Requiring TRX loses users at the first step
A dApp that requires users to hold TRX for gas before they can even try the product loses users right at that first step. But sponsoring transactions yourself usually means running your own energy or staking infrastructure.
Sponsor the interaction, not the infrastructure
Delegate Energy or Bandwidth to a user's address from your dApp's balance right before they sign — no infrastructure of your own to run, no TRX freezing.
Sponsor a specific interaction — mint, swap, claim — with a single call
Smart mode for addresses that interact repeatedly, without a call each time
Scoped keys separate frontend-triggered calls from backend admin actions
Preview endpoint if you want to show the cost before sponsoring
Sponsor a user interaction
Called right before the user signs the interaction you're covering.
solutions.audiences.dapps.integration.codeWhy dApps use this
No TRX ask
Users interact without holding TRX first.
No infra to run
No staking pool or energy management of your own.
Per-interaction or smart
Sponsor one call, or a whole address's usage.
~0.3s
Doesn't add noticeable delay before signing.
Frequently asked questions
Get an API key for your dApp
Scoped keys and daily spend limits from the dashboard — no sales call required to start.