# TRC-721

TRC-721 is a standard interface for issuing non-fungible tokens (NFT) on the TRON network. Tokens created on the TRC-721 standard can represent any digital type of tangible assets in the real world. TRC-721 is fully compatible with ERC-721.

## More opportunities for developers

The TRC-721 standard has as important role for the TRON blockchain as TRC-20. It provides many opportunities for developers to create new applications based on the blockchain, and to track and transfer NFTs on TRON.

<!-- generated:entity-facts -->

## Frequently asked questions

### Which blockchain does TRC-721 run on?

TRC-721 settles on Tron. It keeps ERC-721's per-token-id semantics while settling on Tron, so the same NFT logic applies but the fee model and address format do not.

### What kind of token standard is TRC-721?

It is a non-fungible interface, Tron's counterpart to ERC-721.

### Can I test TRC-721 without spending real funds?

Yes — the same endpoints serve Tron's Nile testnet, so you can build and verify an integration end to end before you touch mainnet.

### How do I read TRC-721 balances and transfers?

Use [Address Latest](/products/blockchain-api/address-latest) for current state and recent activity — it needs no setup and answers for roughly the last 14 days. For a full history, [Address History](/products/blockchain-api/address-history) requires the address to be synced first, which then bills per address per day for as long as it stays synced.

### What does reading TRC-721 data cost?

It depends on the endpoint family rather than on TRC-721 itself: single-record calls are charged per request, while list endpoints are charged per page returned, and a synced address adds a daily monitoring charge. The [pricing calculator](/pricing/calculator) has the current per-chain figures.

<!-- /generated:entity-facts -->

## Related

- [What we support](/what-we-support) · [Contracts Data](/products/blockchain-api/contracts) · [Developer portal](https://developers.cryptoapis.io/)
