What would you check before you buy
that we don't show yet?
If it's on the chain, we can probably read it. If it can't be measured, we'll tell you that instead of pretending. Every request gets a reply from a person, and the ones we build show up in the queue with your wording.
Got it.
We read every one. If it can be built, it goes in the queue with your wording. If it can't, you'll hear why.
What makes a request easy to build
Name the fact, not the feeling. "Share of supply held by wallets under 7 days old" is a fact we can read. "Is this a rug" is an answer we already give, built from facts like that one.
Say what you'd do differently if you knew it. That tells us whether it belongs in a token's answer, the holder map, or our hourly read.
Already in the queue
Creator fees and what the deployer did with them. Our hourly read and a token's full history as tools. Exit route and slippage to ETH for your size. What X is saying. App-wallet share on the holder map. Every rule line recomputed from the record every night. The full list, with what each one needs, is on the docs page.
What we won't build
Anything that buys, sells, or holds a key. Anything that tells you what to do. Anything we can't measure and timestamp.