TemplatesTokensBotsPricing
DashboardStart a build

registry · Robinhood Chain 4663

Stock Tokens on Robinhood Chain, with verified addresses.

196 assets, 194 of them checked for bytecode on chain. The list comes from Robinhood's own API and is synced every fifteen minutes; last sync 3 min ago. Open a token for its contract address, recent transfers, and a one-click Telegram alert. Each contract is also asked for its own symbol and decimals, so a row reads confirmed only when the contract agrees with the listing.

Newest on the chain

Robinhood publishes no listing date, so this is Fletch's own record of when each token appeared. RSS

AllStock TokensStablecoinsWrapped nativeVerified only
SortSymbolNameNewestRecently checked194 shown

Where the list comes from

Robinhood publishes its tokenised assets at a public endpoint. Fletch reads it every fifteen minutes and keeps one row per contract on chain 4663. Nothing is added by hand.

https://api.robinhood.com/rhj/assets

What confirmed means here

Three separate facts. Robinhood publishes the address. The chain returns bytecode at it. The contract answers with the same symbol and decimals as the listing. A row reads confirmed only with all three, and a disagreement is shown rather than hidden. None of this audits what the contract does.

What you can do with a token

Watch it: Fletch messages your Telegram when a transfer above a threshold lands, sequencer-confirmed. Build on it: describe a page for it and Fletch writes and compiles the code.

Create a watcher

For agents and scripts: llms.txt, the assets endpoint, and the new-listings feed.