Home/AI Agents

TRON Energy & Bandwidth for AI Agents

Let your agent buy, delegate and manage TRON resources on its own — with hard limits it can't exceed.

Agents can't babysit a TRX balance

An autonomous agent moving USDT on TRON hits the same wall a human does — run out of Energy and the transfer fails or silently burns TRX at several times the cost. Unlike a human, an agent can't just notice the failure and top up manually; the resource needs to just be there, and there need to be guardrails so a bug or a bad instruction can't drain a wallet.

An API and an MCP server built for that

TronGasAi exposes the same actions two ways: a REST API for custom code, and an MCP server — remote at mcp.trongas.ai/mcp — for agents that speak MCP directly, no custom tool-calling glue required.

Scoped API keys — read, purchase, or full — so a monitoring agent literally cannot spend
Daily spend limits per key, enforced server-side before every charge
Automations (auto-refill, smart) mean the agent sets a policy once instead of polling balance and re-ordering
Idempotency keys make retries safe when an agent's own logic double-calls

Point your MCP client at it

Remote transport, no install — authenticate with the same scoped API key you'd use for the REST API.

{ "mcpServers": { "trongasai": { "url": "https://mcp.trongas.ai/mcp", "headers": { "X-Api-Key": "tgk_4f9a1c8e2b7d..." } } } }

Why agents specifically

Nothing to install
Remote HTTP at mcp.trongas.ai — add the URL and your key, no local process to run.
Least privilege by default
A read-only key can monitor balance and pricing with zero spend risk.
Set-and-forget automations
auto-refill and smart mode keep an address topped up without another call.
~0.3s delegation
An agent's transaction doesn't stall waiting on Energy to land.

Frequently asked questions

MCP is enough — every write tool (buy_energy, create_auto_refill, enable_smart, ...) maps directly to the REST API underneath, so nothing is MCP-only or REST-only.

Yes — issue a read-scope key. Write tools like buy_energy simply aren't available to it.

A daily spend limit on the key, enforced before every charge, plus the fact that scopes are additive — a read key can't be tricked into a purchase call.

Remote (mcp.trongas.ai/mcp) needs no install and works from any MCP client that supports header auth.

Not yet — every call uses your real internal TRX balance. Start with a small daily spend limit while testing.

Get your agent an API key

Free to sign up, scoped keys from the dashboard, full MCP setup guide on docs.trongas.ai.

Get API keyCalculate your savings on your transfer volume →MCP setup guide →