# 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`. We know TRON resources at the level of every block: how Energy is consumed and recovers, how the network counts Bandwidth, how stake behaves on delegation and reclaim. That knowledge became a precise consumption model for every address. 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. ## 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. ## Example: the covered deficit in numbers - In a day the address spent 10M energy. - Its own resource (own stake, earlier rentals) would have covered 4M — that part is not billed. - The other 6M would have burned without us. That is the covered deficit, and that is what is billed. - If something still burned on a served address, it is shown as a separate line and compensated under the contract. - Compare with renting: there you pay for the whole rented volume over time, even if half of it sat idle. ## Products ### Mate Mate follows every address block after block and supplies Energy and Bandwidth before they are needed. You pay for what was consumed. - Payment for what was consumed. The bill holds the Energy and Bandwidth that the address’s transactions consumed from our supply. - Time on the address is free. The resource stays on the address for as long as the flow needs. - Reserve for a burst. Calculated from the past series of the address and placed on it in advance. - Our obligation. Every transaction on a serviced address is provided with the resource — by contract. - Watch mode. A simulation on the live flow shows the operations and the bill before you connect. - Funds under your signature. Your wallet or your system builds and signs the transaction — the private key lives only there. We need the public address alone: we delegate Energy and Bandwidth to it from our stake. Delegation is an operation of the network itself: it adds resource to the address and gives the right to take back only that resource. How it works: 1. Address profile. Seven days of consumption history: the hourly rhythm, series, bursts. 2. Low threshold. The volume that sits on the address in advance, with a reserve for a burst. 3. Top-up. A delegation from our stake up to the high threshold, allowing for demand growth in that hour. 4. Return. When demand falls, the surplus returns to us and keeps working. Questions: - **What does connecting take?** A list of addresses. An address is accepted at once, and your system keeps working as it did. - **How is the bill calculated?** We count the Energy and Bandwidth that the address’s transactions consumed from our supply. The address’s own resource works first and stays yours. - **What does time on the address cost?** Time is free. The resource stays on the address for as long as the flow needs; you pay for consumption. - **How does Mate handle peaks?** The reserve for a burst is calculated from your past series and placed on the address in advance. Providing every transaction is our contractual obligation. - **What does the report show?** By hour: limit, used, consumed, our delegations — Energy and Bandwidth separately. - **How do I stop the service?** With one action in the cabinet. We take the delegations back and the address keeps working on its own resource. https://awesomefee.com/en/products/mate ### Proxy Proxy is a full mirror of a node. You change one line of configuration, and each of your senders receives Energy and Bandwidth at the moment of sending. - A full node mirror. HTTP fullnode, solidity and PBFT, JSON-RPC, gRPC. Responses match those of a TRON node. - Calculation before sending. The node calculates the Energy and Bandwidth of the transaction on our node and supplies the sender with exactly that volume. - The transaction in its original form. Proxy receives the transaction already signed. The signature fixes every field — the recipient, the amount, the contract: the network rejects a changed transaction. We supply the resource to the sender, pass the transaction to the network as is and see exactly what any node of the network sees. - A personal node address. The node serves the list of your senders. You manage the list in the cabinet. - Payment for what was consumed. The same unit as in Mate: the resource the transaction consumed from our supply. - Full transparency. Every broadcast is in the journal: txid, block, Energy, Bandwidth, delegation. How it works: 1. Node address. Replace the node address with your personal node address. 2. Senders. Add sender addresses or take them from Mate. 3. Calculation. The node calculates the Energy and Bandwidth of every transaction. 4. Sending. The resource reaches the sender, the transaction goes to the network in its original form. Questions: - **Where do the keys stay?** With you. Your service builds and signs the transaction, and it reaches the node already signed. The signature fixes every field, so the node passes to the network exactly what it received. - **How does the node treat other addresses?** Transactions of addresses outside your list go to the network as through a regular node. https://awesomefee.com/en/products/proxy ### Direct A mass payout, a listing, a wallet migration. For a planned peak you order the volume for the term you need and know the price in advance. - Any TRON address. The address is accepted at once: just put it in the order. - Price before payment. A quote in SUN per unit for the whole term, the total in TRX. - A term for the task. From 100 to 28,800 blocks: five minutes to a day. - Order control. Early completion and export with txid — in the cabinet and over the API. How it works: 1. Parameters. Address, resource, volume and term. 2. Quote. The price in SUN is fixed while you check out. 3. Payment. From the organization balance in TRX. 4. Delegation. The resource arrives from our stake within the next blocks. Questions: - **Which address can I use?** Any TRON address. It is accepted at once, right in the order. - **Where does the resource come from?** From the own stake of AwesomeFee. https://awesomefee.com/en/products/direct ### Vault Vault takes the resource of your stake and puts it to work on the platform. The TRX stay on your address, and the state of Vault is open to everyone. - The TRX stay with you. You delegate the resource. The stake and the keys stay on your address. - Open state. Vault addresses, delegations, terms and payouts are visible to everyone on this page. - Accruals every day. The reward is calculated from the work of your resource and paid to your address. - A report by address. Enter the address you delegated from — accruals and payouts open at once. How it works: 1. Stake. Freeze TRX for Energy in your wallet. 2. Delegation. Delegate the resource to a Vault address. 3. Accruals. Calculated every day. 4. Payouts. Arrive at your address. Questions: - **Where does a provider see accruals?** On the Vault page by their address; opening the cabinet is optional. https://awesomefee.com/en/vault ## Calculator API GET https://awesomefee.com/api/v1/calc/address/{address}?days=7 - The first request for a new address returns `status: "loading"` with `progress`: the calculation takes up to a minute. Repeat every 2–3 s until the full result arrives. - Use an address that sends transactions itself (a wallet, an exchange or payment-processor hot wallet), not a contract address: a contract has no consumption of its own. - Only `days=7` is public (other values return 403 `PERIOD_NOT_ALLOWED`). ## For AI - [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 - [llms.txt](https://awesomefee.com/en/llms.txt) ## 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. ## Documentation (Markdown) ## AwesomeFee documentation > TRON Energy and Bandwidth for business and AI agents: the API with a key, x402 for agents, Vault for providers. Source: https://awesomefee.com/docs/en/ Every page here is also plain Markdown (add `.md` to its address); the whole documentation in one file is [llms-full.txt](/llms-full.txt). ### Connect - [API: resource on an address with a key](/docs/en/integration/api/) — quote and order Energy and Bandwidth on any address from your code; the organization's balance pays. - [AI agents: TRON resources over x402](/docs/en/agents/overview/) — no account and no key: USDC on Base per call. - [MCP server](/docs/en/agents/mcp/) — the same calls as tools for an assistant. - [How to delegate to Vault](/docs/en/vault/delegate/) — a provider's stake on a pool address, and accruals. ### Machine-readable - [OpenAPI of the agents API (x402)](https://api.awesomefee.com/openapi.yaml), [llms.txt for agents](/agents/llms.txt), [SKILL.md](/agents/SKILL.md) - [llms.txt of the site](/llms.txt), [llms-full.txt](/llms-full.txt) ### Products - [Direct](/en/products/direct) — resource on any address for 1000 blocks, price before payment. - [Mate](/en/products/mate) — resource on your addresses, always: thresholds on every block. - [Proxy](/en/products/proxy) — resource at the moment of sending: change only the node address. - [TRON now](/en/network) — every block of the network: Energy, Bandwidth, TRX burned. ## API: resource on an address with a key > Order Energy and Bandwidth on any TRON address from your code: API key, quote, order, status. Source: https://awesomefee.com/docs/en/integration/api/ Your code orders Energy and Bandwidth on any TRON address through the same API the cabinet runs on. A Direct order keeps the resource on the address for 1000 blocks (≈ 50 minutes); the price is fixed by a quote before the order; the organization's balance pays. | | | |---|---| | API address | `https://cabinet-api.awesomefee.com/api/v1` | | Key | header `X-API-Key`, or `Authorization: Bearer` with an OAuth token | | Organization | `org_…` in the path of every request | | Bodies | JSON | ### Step 0. In the cabinet (a person, once) 1. Sign in to the [cabinet](https://app.awesomefee.com/en/app) and top up the balance of the organization. 2. "API keys" → "Create key". Orders need the `write` scope, reading needs `read`. The secret is shown once. 3. The same screen shows the organization ID (`org_…`) and the API address, each with a copy button. Give the key and the organization ID to your code (or your coding assistant) as `KEY` and `ORG`. **An AI agent without a key** can get access by OAuth instead: it registers with your email, shows you a 6-digit code, you type it in the cabinet and pick the organization and the scopes. Apps and MCP clients use the authorization code flow with PKCE. Both are described in [auth.md](/auth.md); the access appears among your API keys marked "agent" and is revoked there. A key can also be exchanged for a bearer token: `POST https://cabinet-api.awesomefee.com/api/v1/oauth/token` with `grant_type=client_credentials&client_secret=$KEY`. ### Step 1. Quote The price of the amount for 1000 blocks. A quote is valid for 30 seconds. `resource` is `ENERGY` or `BANDWIDTH`. ```bash curl -s -X POST "https://cabinet-api.awesomefee.com/api/v1/orgs/$ORG/quotes" \ -H "X-API-Key: $KEY" -H "Content-Type: application/json" \ -d '{"address":"TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t","resource":"ENERGY","amount":65000}' ``` Answer: `quote_id`, `price_sun` and `price_trx`, `available`, `expires_at`. ### Step 2. Order The body of the quote plus `quote_id`. The `Idempotency-Key` header is required: a repeat with the same key returns the same order (`200`). ```bash curl -s -X POST "https://cabinet-api.awesomefee.com/api/v1/orgs/$ORG/orders" \ -H "X-API-Key: $KEY" -H "Content-Type: application/json" \ -H "Idempotency-Key: payout-2026-11-16-0001" \ -d '{"quote_id":"qt_…","address":"TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t","resource":"ENERGY","amount":65000}' ``` `202` — the order is accepted: `order_id`, `status: ACCEPTED`. ### Step 3. Status ```bash curl -s "https://cabinet-api.awesomefee.com/api/v1/orgs/$ORG/orders/$ORDER" -H "X-API-Key: $KEY" ``` `ACCEPTED` → `PROVISIONING` → `DELIVERED`: the resource is on the address and the transaction goes out with no TRX burned. `PARTIAL` — part of the amount delivered; `FAILED` — nothing delivered, nothing charged. The steps of the order with txids: `GET /orgs/$ORG/orders/$ORDER/events`. ### Resource on your addresses, always: Mate For a constant flow, put the addresses into Mate: - `POST /orgs/{orgId}/addresses` — add an address: `{"address":"T…","label":"payouts"}`; - `PUT /orgs/{orgId}/addresses/{address}/scenario` — the mode: `{"mode":"watch"}` or `{"mode":"serve"}`; - `GET /orgs/{orgId}/addresses/{address}/usage` — consumption by hour; `…/burns` — TRX burned; `…/delegations` — our delegations on the address. ### Other calls with a key - `GET /orgs/{orgId}/orders` — orders with filters; `GET /orgs/{orgId}/orders/export.csv`. - `GET /orgs/{orgId}/orders/{id}/reclaim-preview`, `POST /orgs/{orgId}/orders/{id}/reclaim` — early reclaim. - `GET /orgs/{orgId}/balance`, `GET /orgs/{orgId}/balance/history`. - `GET /tron/addresses/{address}/check`, `GET /tron/addresses/{address}/preview` — any address: format, activation, live resources, TRX burned in 24 h. - `GET /orgs/{orgId}/api-limits`, `GET /orgs/{orgId}/api-usage` — the limits and the use of the key. ### Errors An error is JSON `{"error":"","code":""}` with the HTTP status: | Status | Codes | |---|---| | 400 | `VALIDATION_ERROR`, `INVALID_ADDRESS`, `AMOUNT_BELOW_MIN`, `DURATION_FIXED` (Direct: 1000 blocks only) | | 401 | no key, a revoked or expired key | | 402 | `INSUFFICIENT_BALANCE` | | 403 | `FORBIDDEN_ROLE` (the key's scope), `ADDRESS_NOT_ALLOWED` | | 409 | `QUOTE_EXPIRED`, `IDEMPOTENCY_CONFLICT`, `NOT_RECLAIMABLE` | | 429 | the key's limit; wait `Retry-After` | | 503 | `NO_CAPACITY`, `UPSTREAM_UNAVAILABLE`; retry after `Retry-After` | Without an account, paying per call in USDC: [AI agents and x402](/docs/en/agents/overview/). ## AI agents: TRON resources via x402 > Energy, transaction sending and node access for agents, paid per call in USDC on Base. No account, no key. Source: https://awesomefee.com/docs/en/agents/overview/ An agent that has to move USDT or call a contract on TRON gets the resource from AwesomeFee in one HTTP exchange and pays for it in USDC on Base with the [x402](https://x402.org) protocol (version 2). No registration, no API key, no balance with us. The payer signs a USDC authorization (EIP-3009) and pays no gas; the TRON sender needs no TRX. API: `https://api.awesomefee.com` · [OpenAPI](https://api.awesomefee.com/openapi.yaml) · [llms.txt for agents](/agents/llms.txt) · [Skill (SKILL.md)](/agents/SKILL.md) · [Everything in one file](/agents/llms-full.txt) ### How it works 1. **Find:** `GET https://api.awesomefee.com/v1/search?q=` — free; returns catalogue entries (`id`, `method`, `url`, `parameters`, `price`, `payment`: free | x402 | pass, a curl `example`); no `q` = the whole catalogue. 2. **Call** the URL with an x402 v2 HTTP client (`@x402/fetch`, `@x402/axios`, Python `x402`). 3. **On 402** the client pays the USDC terms from the agent's own wallet and repeats the request. 4. **Get the result.** ### What is sold | Endpoint | What the agent gets | Payment | |---|---|---| | `GET /v1/search?q=` | the product URL for a need, with method, input and price — start here | free | | `GET /x402/v1/quote` | price of energy or sending (with `burn_equivalent`), pass tiers | free | | `POST /x402/v1/tron/estimate` | energy and bandwidth of a transaction, what the sender already has, what is missing, the price | free | | `GET /x402/v1/address/{address}` | what the address spent and burned over 7 days | free | | `POST /x402/v1/tron/send` | **sending with energy included**: the agent posts its signed transaction; we delegate the missing energy to the sender, broadcast the transaction unchanged and answer `txid` and the block | x402 | | `POST /x402/v1/tron/energy` | energy to any address for 1000 blocks (~50 min) | x402 | | `POST /x402/v1/proxy/pass` | prepaid pass: broadcasts through our Proxy (`/proxy/wallet/broadcasttransaction`), energy before every transaction of the bound senders, at the agent price | x402 | | `POST /x402/v1/rpc/pass` | prepaid reads of a full TRON node at `/rpc` (TronWeb `fullHost` + `TRON-PRO-API-KEY`), full history | x402 | | `POST /x402/v1/events/sub` | prepaid events of TRON addresses: transfers, delegations, resource use; webhook or WebSocket at `/v1/events` | x402 | | `GET /x402/v1/pass` | balance of a pass (`Authorization: Bearer `) | free | | `GET /x402/v1/payments/{id}` | state of a paid order and its refund | free | `tier` is the tier name or its USDC price. The answer: `pass_id`, `token` (`tlp_…`, keep it), `tier`, `unit`, `added_credits`, `expires_at`, `limits`, `rpc_url` or `events_url`, `balance_url`. Buying again with the token as `Authorization: Bearer` tops the pass up. Everything sold: `GET /x402/v1`. ### Prices - **Agent price** — a sale price: in USDC at the live TRX/USD rate, known before payment (`GET /x402/v1/quote`). - Every quote carries **`burn_equivalent_sun`** and **`burn_equivalent_usd`**: what the sender would burn without us (100 SUN per energy unit; a USDT transfer needs about 64 285 energy, to an address that never held USDT about 130 285). - Quotes, transaction estimates, address analysis, pass balances and order states are free. - Node reads: credits per call (1 for ordinary calls, 2–10 for heavy ones); events: 1 credit per delivered event. ### Pass tiers | Pass | Tier (name or USDC) | What you get | Days | |---|---|---|---| | Node reads | rpc-trial · rpc-s · rpc-m · rpc-l · rpc-xl (0.5 · 9 · 35 · 120 · 300) | 50 000 · 1M · 5M · 20M · 60M credits; 5 · 10 · 25 · 50 · 100 rps | 7 for 0.5, else 30 | | Address events | ev-s · ev-m · ev-l (3 · 15 · 60) | 10 · 100 · 1 000 addresses; 200 000 · 2M · 10M events | 30 | | Proxy | proxy-5 · proxy-20 · proxy-100 (5 · 20 · 100) | credits in USDC; energy for each transaction of up to 5 bound senders, at the agent price | 30 | ### The payment cycle ```text agent → POST https://api.awesomefee.com/x402/v1/tron/send {"signed_tx": {…}} ← 402 PAYMENT-REQUIRED: base64 {"x402Version":2,"accepts":[{"scheme":"exact","network":"eip155:8453", "amount":"","asset":"","payTo":"0x…", …}]} agent signs one "accepts" entry with its wallet (EIP-3009, offline, no gas) agent → POST https://api.awesomefee.com/x402/v1/tron/send {"signed_tx": {…}} + PAYMENT-SIGNATURE: base64 PaymentPayload ← 200 {"status":"confirmed","txid":"…","block":…,"result":"SUCCESS","energy_used":64285,"energy_burned_sun":0} (202 {"status":"pending","status_url":"…/x402/v1/payments/xp_…"} — paid, still running) PAYMENT-RESPONSE: base64 {"success":true,"transaction":"0x…","network":"eip155:8453","payer":"0x…"} ``` Any x402 v2 client does this: `@x402/fetch`, `@x402/axios`, Python `x402`. Examples: [curl](/agents/examples/curl.sh) (with the [signer](/agents/examples/sign-x402.mjs)), [@x402/fetch](/agents/examples/x402-fetch.mjs), [@x402/axios](/agents/examples/x402-axios.mjs), [Python](/agents/examples/x402_requests.py). ### Refusals and refunds - Checked **before** the 402, nothing is charged: expired transaction, a call that would revert, a transaction type outside TRX / TRC-20 and contract calls / TRC-10, a sender that is not activated, more than 300 000 energy, not enough bandwidth of the sender's own (bandwidth is not sold yet), no capacity, rate limit. - Paid but not delivered by our fault — the USDC goes back to the payer automatically. - Delivered but the agent's transaction reverted on chain — no refund: the resource was used. - The same payment repeated returns the same answer. ### Discovery - MCP server: `https://api.awesomefee.com/mcp` — one `search` tool and these docs as resources, see [MCP server](/docs/en/agents/mcp/). - `https://api.awesomefee.com/.well-known/x402` — x402 manifest; `https://api.awesomefee.com/.well-known/ai-catalog.json` and `https://api.awesomefee.com/mcp/server-card` — MCP discovery. ## AI agents: MCP server > A thin directory: one search tool and the agent docs as resources; payment happens on the product URLs. Source: https://awesomefee.com/docs/en/agents/mcp/ The MCP server is a directory, nothing more: one tool **`search`** (the same `GET https://api.awesomefee.com/v1/search?q=`) and the agent docs as resources (`llms.txt`, `SKILL.md`, OpenAPI). It does not pay, does not execute and holds no keys. The agent takes the product URL from `search`, calls it with its own x402 v2 HTTP client, pays on 402 and gets the result — the same cycle as without MCP ([overview](/docs/en/agents/overview/)). ### Remote `https://api.awesomefee.com/mcp` — Streamable HTTP, stateless (no sessions), current MCP revision; 2025-era clients work too. ```json { "mcpServers": { "tron-x402": { "type": "http", "url": "https://api.awesomefee.com/mcp" } } } ``` ### Local ```json { "mcpServers": { "tron-x402": { "command": "npx", "args": ["-y", "tron-x402-mcp"], "env": { "TRON_X402_API_URL": "https://api.awesomefee.com" } } } } ``` ### Discovery `https://api.awesomefee.com/.well-known/ai-catalog.json` → server card `https://api.awesomefee.com/mcp/server-card`; x402 manifest `https://api.awesomefee.com/.well-known/x402`. ## How to delegate to Vault > Delegate the resource of your stake to a Vault pool address. Source: https://awesomefee.com/docs/en/vault/delegate/ ### Steps Freeze TRX for energy, then delegate the resource to a pool address from your wallet. ### No cabinet Providers need no cabinet: accruals are on the site by address. ### Pool addresses and accruals Pool addresses, terms and the accruals of your address are on the [Vault](/en/vault) page of the site.