$MERCURY MERCURY
0x83f301c1993c4ce87a6f836539588a0e93dc15ef
0x83f301c1993c4ce87a6f836539588a0e93dc15ef
Not yet known. Its X account and website don't list this contract (yet).
Nothing official lists this contract yet. Dossier keeps checking for 72 hours after launch; the official post often lands a few minutes after the token.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
Dossier’s readUtility
Mercury writes LinkedIn content from source to sign-off, AI-powered by Orbio.
An AI summary of what the launcher’s description, the X account and the site say. It describes; the verdict above is what vouches.
LinkedIn content, from source to sign-off. Al powered by @orbiodotso
The token description, written by whoever launched it.
0/100
Nothing it points at claims it (yet).
In launch order, coloured by verdict. This one is ringed.
From the chain alone: holder counts are real end buyers, not routers or bots, and bots are wallets that buy 10 or more launches a day.
Trading fees fund this agent: half is staked as ORBIO and earns CREDIT, 30% is minted to it as CREDIT, 10% becomes a balance it can spend on models and tools, and 10% goes to Orbio.
The accounts and sites in the token's own metadata, and whether each one claims this token. Metadata is written by the launcher, so only the claim counts. Dossier reads them throughout a launch's first day. After that it reads them again while people trade the token or look at its file: opening a file last read over a day ago queues a fresh read.
| Kind | Link | Claims it? |
|---|---|---|
| Website | usemercury.xyz | named
read |
| X account | x.com/mercuryorb | named
read |
Raw data for this file: 0x83f301c1….json