Fletch
Docs
Connecting

Token registry

208 recorded assets, including 195 Stock Tokens. 206 checked on chain. Latest asset-source observation 14 min ago.

JSONToken markets
208 matching of 208
Listing confirmed
How to read the registry

Match the full address before using a token. Identity badges describe listing checks. Feed price is a USD reference; Markets shows trading-pool prices. Each reading has its own source and age.

Where the list comes from

Stock Token addresses come from Robinhood's public asset list, checked every fifteen minutes. Bridged assets come from recorded gateway mappings. Fletch keeps one row per contract on chain 4663, with each source's observation time.

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

What verified 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 verified 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.