$DELIVERD deliverd
0xa3b5786803c342b6cba2e18480beab1103346ad8
0xa3b5786803c342b6cba2e18480beab1103346ad8
Not yet known. The accounts and sites it names haven't been read 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
Deliverd adds human approval gates and audit records so AI agents ask before acting, for teams using Slack, Teams or email.
An AI summary of what the launcher’s description, the X account and the site say. It describes; the verdict above is what vouches.
The secure delivery layer for AI-generated work.
The token description, written by whoever launched it.
0/100
Orbio vault launch: skips the stage 0/1 filters.
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 | deliverd.dev | not checked |
| X account | x.com/deliverd_dev | not checked |
Raw data for this file: 0xa3b57868….json