Pasting a contract address
Pasting a contract address
Pasting a contract address or a recognised link is the trigger — there is no scanner command. The bot replies with the coin's card, or not at all if nothing resolves.
The trigger
There is no command. Pasting a contract address, or a link the bot recognises (chapter 3.2), into a chat is the trigger. The bot replies with the coin's card (chapter 3.3).
The scanner only answers when it's switched on for the bot. It is off by default.
- Message text. Any text is scanned once it doesn't match a registered command.
- Photo caption. A photo carrying no text of its own — only a caption — is scanned from that caption instead.
Hidden links count too. A text_link is a URL sitting behind display text — a word or phrase hyperlinked in the message with no visible URL. The bot reads a hidden text_link the same as a plainly pasted one, from either the message text or a photo caption.
Never scanned
A message starting with
/is never scanned — even a/-line the bot doesn't recognise as a command. Leading whitespace is stripped before the check runs, so/foo 0x1234…is skipped too.
A message addressed to another bot (/cmd@otherbot) is dropped before the scanner is reached.
The scanner never blocks the rest of the message: it answers in the background, so an image-generation trigger word in the same message still produces an image.
The card is sent as a reply to your message, with notifications and link previews switched off.
Addresses that don't resolve
No reply at all
An address or link that doesn't resolve to a token gets no reply of any kind — not an error message, nothing. A wallet address, a dead pair link, and an unlisted token all fail the same way: silently.
The two ways of failing are remembered differently. A candidate that resolves with no price and no symbol is remembered as a miss and answered with silence every time it's pasted again. A transient failure — a timeout, an RPC that didn't answer in time — is not remembered; pasting the same text again retries it from scratch.
No quantity caps
Deliberately uncapped
The scanner enforces no burst cap, no per-message cap, and no repeat cooldown.
- No burst cap. There's no limit on how many pastes a chat can trigger in a short window.
- No per-message cap. Every candidate in a message gets its own card, in the order it appears — three different contract addresses in one message produce three separate replies.
- No repeat cooldown. Pasting the same address again immediately still gets a reply every time; a reply is never suppressed for being recent.
The one place multiple mentions fold together is inside a single message: the same address pasted twice in one message produces one card, not two. If the second copy names a chain the first copy didn't (for example a bare 0x… followed later in the same message by a link that names its chain), that chain is applied to the existing card instead of adding a second one.