TronGrid

TronGrid is a hosted node service for the TRON network. Its role is similar to Infura or Alchemy in the Ethereum ecosystem: developers can connect to TRON through HTTPS or gRPC endpoints without deploying and maintaining their own nodes. Applications can read chain state, build and broadcast transactions, and connect common tooling through managed endpoints.

In addition to standard node endpoints, TronGrid provides pre-indexed extension APIs for data that standard node APIs do not expose directly, such as account history, Token transfers, contract events, and internal transactions.

TronGrid has two main capabilities:

Capability	Description
Node service	Provides FullNode HTTP, SolidityNode HTTP, JSON-RPC, and gRPC endpoints for transaction construction, broadcast, chain-state reads, and tooling integration.
Extension APIs	Provides TronGrid V1 API for pre-indexed account history, TRC-20 transfers, contract events, internal transactions, Token balances, and block statistics.

Main website and console entry points:

Resource	Link
TronGrid website	https://www.trongrid.io
Shasta Testnet	https://www.trongrid.io/shasta
API key / quota management	Manage after logging in to the TronGrid console

📘
Prerequisites

Tools and SDKs

API reference

Node service

As a hosted node service, TronGrid proxies standard TRON node interfaces:

API type	Typical use
FullNode HTTP API	Build transactions, broadcast transactions, read latest head state
SolidityNode HTTP API	Read solidified transactions, accounts, and blocks
JSON-RPC API	Connect ethers, web3.js, viem, and other Ethereum-compatible tooling
gRPC API	Call native TRON gRPC interfaces from server-side programs

Choose FullNode or SolidityNode based on whether the read must be final. Transaction construction and broadcast usually use FullNode. Transaction confirmation, balance reconciliation, and solidified block reads should use SolidityNode. For details, see FullNode and SolidityNode selection guide.

For common network endpoints, see Networks. For gRPC examples, see Calling TRON via gRPC.

Extension APIs

TronGrid V1 API is the pre-indexed query layer that TronGrid provides in addition to standard node APIs. It is useful for querying historical data by account, contract, Token, event, or block without scanning and parsing every block yourself.

Common query targets include:

Query target	Reference entry
V1 API categories and entry points	TronGrid V1 API overview
Account state and transaction history	Accounts and transactions
TRC-20 / TRC-721 transfer history	Get contract transaction information by account address
Contract event logs	Events
Internal transactions	Get internal transactions by address

Extension APIs are index services, not the consensus layer itself. When final state is required, use confirmation parameters, pagination cursors, local de-duplication, and solidified-state checks where needed.

AI agent access

In addition to direct HTTP and gRPC calls, TronGrid offers higher-level access surfaces for AI agents and command-line workflows. These wrap the same underlying APIs, so they share the same API key, networks, and rate limits.

Surface	What it is	Entry
MCP server	A hosted Model Context Protocol server that exposes TRON queries and operations as standardized MCP tools, for clients such as Claude, Cursor, and custom agents.	MCP server
AI agent skills	Pre-built natural-language workflows (account profiling, token scanning, transaction decoding, and more) that an agent runs on top of the MCP server.	AI agent skills
CLI	`trongrid-cli`, a command-line interface for read-side TRON queries, with a `--json` mode for agents and scripts.	CLI

API key

Production use of TronGrid should configure an API key. The API key is used for identification, quota tracking, rate limiting, and security settings. It does not represent on-chain account permissions and does not sign transactions for the application.

For API key creation, network endpoints, and request header format, see API Key. For security settings such as Origin, User-Agent, API allowlists, and JWT, see Security settings.

Rate limit

TronGrid may limit requests by API key, account, IP, endpoint type, and time window. Rate-limited requests may return 429 or 403. Clients should use backoff, caching, pagination, and checkpointed scans instead of polling the same address or block range at high frequency.

For rate-limit dimensions, error responses, retry strategy, and quota increase workflow, see TronGrid rate limits.

Relationship with self-hosted nodes

TronGrid and self-hosted nodes are not mutually exclusive. TronGrid is useful for fast integration, testnet development, backup endpoints, and pre-indexed historical queries. Self-hosted nodes are useful for production paths that need high control, internal auditability, dedicated indexing, or custom node configuration.

Dimension	TronGrid	Self-hosted node
Operations cost	No node sync or maintenance required	Requires deployment, sync, monitoring, and upgrades
Standard node APIs	Called through hosted endpoints	Provided directly by the local java-tron node
Historical queries	V1 API provides pre-indexed queries	Requires a self-hosted indexer or block scanning
Control	Affected by service policies, quotas, and rate limits	Control over node configuration, data retention, and access policy

For tradeoffs between hosted RPC, self-hosted nodes, and indexers, see RPC and indexer providers.

Related resources

TronGrid V1 API overview — extension API categories and entry points
MCP server — TronGrid MCP server for AI clients
AI agent skills — pre-built natural-language workflows
CLI — trongrid-cli, the command-line interface for read-side queries
API Key — network endpoints, API key creation, and request header format
TronGrid rate limits — quota, 429 / 403, backoff, and quota increase workflow
FullNode HTTP API — standard node read/write APIs
Solidity HTTP API — solidified-state read APIs
JSON-RPC API — Ethereum-compatible tooling entry point
Networks — Mainnet, Shasta, and Nile endpoints
RPC and indexer providers — choosing hosted RPC, self-hosted nodes, and indexers