# AwesomeFee — TRON Energy and Bandwidth for business and AI agents > AwesomeFee keeps Energy and Bandwidth on the addresses of businesses with a heavy transaction flow — exactly to consumption, block after block. Mate runs addresses, Proxy supplies the resource at the moment of sending. You pay for what was consumed; in Mate the time a resource stays on the address is free. ## AI agents: buy TRON resources (x402) Unprecedented terms for agents: TRON resources over x402 at sale prices, micropayments and node data at the lowest price. All for our helpers. API https://api.awesomefee.com. Paid calls use x402 v2: USDC on Base (eip155:8453), scheme exact. No account, no API key. 1. Find the product: `GET https://api.awesomefee.com/v1/search?q=energy` — every result carries the URL, method, parameters, price and an example. 2. Get the price: `GET https://api.awesomefee.com/x402/v1/quote?product=energy&amount=65000`. 3. Call: `POST https://api.awesomefee.com/x402/v1/tron/energy` with body `{"address":"T…","amount":65000}` (65,000–300,000 energy for 1000 blocks ≈ 50 min) → HTTP 402, header `PAYMENT-REQUIRED` (base64 JSON, `accepts[0]`: exact, eip155:8453, USDC, amount, `payTo`, 60 s). 4. Pay: sign an EIP-3009 `transferWithAuthorization` for USDC on Base and repeat the same request with header `PAYMENT-SIGNATURE` → 200 with the result and `PAYMENT-RESPONSE`. 202 means processing: poll `GET https://api.awesomefee.com/x402/v1/payments/{payment_id}`, pay once. 5. Check: the energy is delegated to the address on TRON — send the transaction as usual. Also: `POST https://api.awesomefee.com/x402/v1/tron/send` — a signed transaction is sent with the resource supplied; passes `proxy/pass`, `rpc/pass`, `events/sub`. There is always enough resource — we stay one step ahead. Our services see the consumption of every address block by block and place Energy and Bandwidth in advance: when a transaction goes out, the resource is already on the address. The reserve for bursts is ours. ## What problems we solve Every TRON transaction spends Energy and Bandwidth. When they run short, the network burns the sender’s TRX. Own stake and a rented stock solve the task at a high price. - **TRX burning.** A USDT transfer from an empty address pays the network price in burned TRX, transfer after transfer. - **Idle stock.** Own stake or rent is held with a margin and paid in full, working or waiting. - **Bursts.** A fixed stock stays fixed while demand grows: in busy hours the address burns TRX. - **Manual work.** Thresholds, rent renewals, switching suppliers, reconciliation — a constant operational load on the team. ## How it differs from renting Rent is payment for a volume over time, used or not. With us you pay for what was consumed: only the Energy and Bandwidth the address actually consumed from our supply. In Mate the time a resource stays on the address is free. The reserve for bursts and its idle time are our concern; burning on a serviced address is our responsibility. ## Products - [Mate](https://awesomefee.com/en/products/mate): We keep Energy and Bandwidth on your addresses to their consumption, block after block. You pay for what was consumed; time on the address is free. - [Proxy](https://awesomefee.com/en/products/proxy): A TRON node mirror: it provides the sender with the resource and passes the transaction to the network in its original form. - [Direct](https://awesomefee.com/en/products/direct): Energy and Bandwidth on any address for a set term, with the price known in advance. - [Vault](https://awesomefee.com/en/vault): The resource of your stake works, the TRX stay on your address. ## Key terms - Covered deficit — the billing unit of Mate and Proxy. The address is modelled without our delegation; whatever would have burned in that model (energy and bandwidth) is billed. Resource the address would have had anyway is not billed. - Burning TRX on a served address for a served resource is the responsibility of AwesomeFee; it is shown as a separate line and compensated under the contract. - Watch mode — Mate runs as a simulation: an operations log marked “simulation”, nothing is sent to the network. The client sees the result before connecting. - AwesomeFee never holds client keys and never signs or changes client transactions. - Only AwesomeFee delegates to client addresses, from its own stake. Resource received through Vault is never passed on to clients. - Mate and Proxy are priced per address by its consumption; the price is not on the site. Use the calculator to evaluate, the contacts page for terms. - Direct and Vault copy is preliminary; their terms are not final yet. ## For AI - [llms-full.txt](https://awesomefee.com/en/llms-full.txt): Full version: products, questions, worked example, API - [AwesomeFee Services SKILL.md](https://awesomefee.com/en/skills/services/SKILL.md): Skill “AwesomeFee Services”: products, billing, matching a product to an address - [TRON Resources SKILL.md](https://awesomefee.com/en/calculator/skills/tron-resources/SKILL.md): Skill “TRON Resources”: energy and bandwidth mechanics (limit, used, recovery, burning) - [calculator/llms.txt](https://awesomefee.com/en/calculator/llms.txt): Calculator llms.txt: what it computes and how to read the results - Calculator API: GET https://awesomefee.com/api/v1/calc/address/{address}?days=7 ## For AI agents (x402) - [x402](https://awesomefee.com/docs/en/agents/overview/): x402 documentation: USDC payment on Base right in the request, products and examples - [agents/llms.txt](https://awesomefee.com/agents/llms.txt): the agent file: products, prices, the call order - [OpenAPI x402](https://awesomefee.com/agents/openapi.yaml): the x402 API description - [MCP](https://awesomefee.com/docs/en/agents/mcp/): MCP server: the search tool and the documents as resources - GET https://api.awesomefee.com/v1/search: product catalog, the agent’s first step ## Documentation (Markdown) - [AwesomeFee documentation](https://awesomefee.com/docs/en/index.md): TRON Energy and Bandwidth for business and AI agents: the API with a key, x402 for agents, Vault for providers. - [API: resource on an address with a key](https://awesomefee.com/docs/en/integration/api.md): Order Energy and Bandwidth on any TRON address from your code: API key, quote, order, status. - [AI agents: TRON resources via x402](https://awesomefee.com/docs/en/agents/overview.md): Energy, transaction sending and node access for agents, paid per call in USDC on Base. No account, no key. - [AI agents: MCP server](https://awesomefee.com/docs/en/agents/mcp.md): A thin directory: one search tool and the agent docs as resources; payment happens on the product URLs. - [How to delegate to Vault](https://awesomefee.com/docs/en/vault/delegate.md): Delegate the resource of your stake to a Vault pool address. ## Pages - [Home](https://awesomefee.com/en) - [Address analysis](https://awesomefee.com/en/tools/address-analysis): Resource calculator: TRON address → consumption, idle stock, burned TRX - [AI Agents & x402](https://awesomefee.com/en/agents): One HTTP exchange: request, USDC payment, executed transaction. - [Contacts](https://awesomefee.com/en/contacts): Contacts and a request for terms ## Legal - [General Terms of Service](https://awesomefee.com/en/legal/terms-general): Terms of use of the site, the cabinet and the API. - [Terms of Resource Service](https://awesomefee.com/en/legal/terms): Service for addresses: Mate, Proxy and Direct. - [Terms of Vault](https://awesomefee.com/en/legal/terms-vault): For stake providers: delegation, accruals, payouts. - [Privacy Policy](https://awesomefee.com/en/legal/privacy): What data we collect, how we store it and how we use it. - [AML policy](https://awesomefee.com/en/legal/aml): Anti-money-laundering rules and customer checks. ## Optional - [Documentation](https://awesomefee.com/docs/en) - [Русская версия](https://awesomefee.com/ru/llms.txt)