05 · Ask the grub
Give it a hash, an address, a token, calldata, a link or a question.
Planner, not oracle
A deterministic planner reads the message for hashes, addresses, calldata, links and keywords, and picks tools:
| Tool | Triggered by |
|---|---|
get_gas | gas, fee, gwei |
get_price | BNB price |
lookup_transaction | a 32-byte hash: status, call, value, fee, token transfers |
explain_calldata | an address plus calldata: decode, replay, verdict |
check_token | an address with token / honeypot / tax / buy / sell words |
whois | any other address: wallet or contract, name tag, verified, token or not, flagged |
check_approvals | approval, allowance, revoke |
wallet_balances | balance, portfolio, holdings |
scam_check | scam words or a link |
grub_info | questions about $GRUB |
position_size | account, risk % and stop % |
Tools run in your browser against the chain. The answer is composed from their results, so every number in it comes from a tool. The tool trace (name, success, latency) is printed under each answer.
Server brain (optional)
The operator can set an ANTHROPIC_API_KEY on the server. When present, holders of 5 M GRUB (or anyone with ?brain in the URL) get the composed answer rewritten by a language model that receives only the tool results and the draft, with the instruction to invent nothing. Without the key the endpoint answers nothing and the page shows brain: rules. The rules answer is the product; the model is a stylist.