Skip to content
AwesomeFee
ru Cabinet

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.

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 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 · llms.txt for agents · Skill (SKILL.md) · Everything in one file

How it works

  1. Find: GET https://api.awesomefee.com/v1/search?q=<what you need> — 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

EndpointWhat the agent getsPayment
GET /v1/search?q=the product URL for a need, with method, input and price — start herefree
GET /x402/v1/quoteprice of energy or sending (with burn_equivalent), pass tiersfree
POST /x402/v1/tron/estimateenergy and bandwidth of a transaction, what the sender already has, what is missing, the pricefree
GET /x402/v1/address/{address}what the address spent and burned over 7 daysfree
POST /x402/v1/tron/sendsending 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 blockx402
POST /x402/v1/tron/energyenergy to any address for 1000 blocks (~50 min)x402
POST /x402/v1/proxy/passprepaid pass: broadcasts through our Proxy (/proxy/wallet/broadcasttransaction), energy before every transaction of the bound senders, at the agent pricex402
POST /x402/v1/rpc/passprepaid reads of a full TRON node at /rpc (TronWeb fullHost + TRON-PRO-API-KEY), full historyx402
POST /x402/v1/events/subprepaid events of TRON addresses: transfers, delegations, resource use; webhook or WebSocket at /v1/eventsx402
GET /x402/v1/passbalance of a pass (Authorization: Bearer <token>)free
GET /x402/v1/payments/{id}state of a paid order and its refundfree

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

PassTier (name or USDC)What you getDays
Node readsrpc-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 rps7 for 0.5, else 30
Address eventsev-s · ev-m · ev-l (3 · 15 · 60)10 · 100 · 1 000 addresses; 200 000 · 2M · 10M events30
Proxyproxy-5 · proxy-20 · proxy-100 (5 · 20 · 100)credits in USDC; energy for each transaction of up to 5 bound senders, at the agent price30

The payment cycle

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":"<USDC, 6 decimals>","asset":"<USDC>","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 (with the signer), @x402/fetch, @x402/axios, Python.

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.
  • 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.