Your TRON application sends RPC calls somewhere — to read on-chain data, broadcast transactions, subscribe to events. The endpoint can be your own full node, TronGrid (the most widely used hosted service in the TRON ecosystem), or a third-party RPC provider. This page lays out the options, the comparison dimensions, and indexer services that operate on top of raw chain data.

📘
Prerequisites

Networks

1. Self-hosted or hosted?

Dimension	Self-hosted full node	Hosted node service
Startup cost	High (hardware, ops, monitoring)	Low (API key, integrate)
Recurring cost	Hardware, bandwidth, ops time	Plan-based — free tier available
Latency control	Yours	Provider's
Rate limits	None (your hardware caps)	Tiered (free → enterprise)
Custom indexing	Build whatever you want	Limited to what the provider exposes
Resilience	Single point of failure unless you build HA	Provider's SLA
Code coupling	Standard wire format	Same wire format — easy to migrate

Rule of thumb: start with hosted. Migrate to self-hosted when rate limits constrain you, you need custom block parsing or indexing the host does not offer, or the cost crossover favors operating your own node.

For self-hosted setup, see Deploy a node.

2. Hosted RPC providers

TRON's wire format (POST /wallet/... over HTTP) is consistent across providers — switching endpoints does not require code changes.

TronGrid

TronGrid is a widely used hosted node service in the TRON ecosystem. It provides FullNode, SolidityNode, JSON-RPC, and gRPC endpoints, plus extension APIs such as account history, TRC-20 transfer history, and contract event logs.

API key: required for production traffic. See API Key.
Rate limits: request quota and frequency limits may vary by plan and service policy. See TronGrid rate limits.
Networks: Mainnet, Shasta, Nile

Third-party providers

Eight hosted RPC providers serve TRON Mainnet, plus Chainstack also covers the Nile testnet. The full table with links and current coverage notes lives in Networks § Third-party RPC providers — refer to it rather than maintaining a duplicate list here.

3. Comparison dimensions

If you have chosen hosted, here is how to compare:

Free tier limits — daily request cap, peak QPS, supported endpoint families
TRON-specific endpoints — does the provider expose triggerconstantcontract, getaccountresource, and other TRON-specific calls, or only the generic subset?
Extension APIs — currently, only TronGrid exposes pre-indexed account-history endpoints
Geographic latency — where are the provider's nodes? Test from your deployment region
Archive access — do you need historical state? Most free tiers do not include archive nodes
Pricing model — request-count, QPS-tier, or volume-based?

4. Indexer and data services

RPC services return raw chain data. Indexer services return queryable structured data — token transfers per address, event logs filtered by topic, balance history over time.

TronGrid extension APIs

The fastest path. TronGrid exposes account-level history and TRC-20 history endpoints; these are pre-indexed and bypass raw block parsing.

Endpoint	Returns
`v1/accounts/{address}/transactions`	TRX and TRC-10 history for an address
`v1/accounts/{address}/transactions/trc20`	TRC-20 history for an address
`v1/contracts/{address}/events`	Event logs for a smart contract

TRONSCAN APIs

TRONSCAN — TRON's public block explorer — exposes API endpoints suitable for ad-hoc queries: token metadata, transaction lookups, address activity. They are not designed as a primary infrastructure dependency for production loads.

Third-party indexers

The TRON ecosystem currently lacks a widely-adopted decentralized indexer equivalent to The Graph on Ethereum. Most teams whose indexing needs exceed TronGrid's extension APIs roll their own indexer over a self-hosted full node:

Run a full node with vm.saveInternalTx = true
Parse blocks as they finalize (see Exchange wallet integration § Parsing blocks)
Stream parsed events to your database

5. Block-explorer APIs

Block explorers expose convenience APIs useful for development tools and ad-hoc queries.

Explorer	API base	Useful for
TRONSCAN	`https://apilist.tronscanapi.com`	Token metadata, transaction lookups, address activity

Block-explorer APIs have separate rate limits and operational policies; do not depend on them for production transaction flow.

Related resources

Networks — Mainnet, Shasta, Nile endpoints
TronGrid — TronGrid node service and extension API introduction
API Key — create API keys, choose network endpoints, and configure request headers
TronGrid rate limits — request quotas, 429 / 403 responses, and backoff strategy
Deploy a node — self-hosted setup
Exchange wallet integration — combined integration guide