$AFFECTUI AffectUI
0x5d0b05cfc95a80d751dc5e90b17d3d409516bc08
0x5d0b05cfc95a80d751dc5e90b17d3d409516bc08
Not confirmed. Its X account and website don't list this contract (yet).
Nothing official lists this contract. That isn't proof of a scam, but no one has claimed it.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
Dossier’s readUtility
AffectUI sells React components for AI products, letting agents and developers add agent-ready UI via shadcn CLI or MCP.
An AI summary of what the launcher’s description, the X account and the site say. It describes; the verdict above is what vouches.
UI for AI agents 30 React components for what agents do, and 99+ for the rest of your app – one file each.
The token description, written by whoever launched it.
0/100
Nothing it points at claims it (yet).
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 | www.affectui.com | named
read |
| X account | x.com/affectui | unbound
read |
Raw data for this file: 0x5d0b05cf….json