$ORBJ Orbject
0x96e724abeb3861e4691649cd3b9d542021654e8b
0x96e724abeb3861e4691649cd3b9d542021654e8b
Yes. The official account @orbjectai posted and the official site orbject.store lists this contract.
The project's own X account or website lists this exact contract.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
Dossier’s readUtility
AI agent on Orbio turns tasks into budget-capped objects, checks results with a second model, and pays from Orbio credits.
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 token of Orbject, an AI agent on Orbio that turns every task into an object and checks the result before it lands. Holders get priority orbits and free daily objects.
The token description, written by whoever launched it.
0/100
Claimed by @orbjectai, orbject.store; waiting for a dossier.
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.
Apps the sites on this file sign people in to, as Orbio’s own consent screen describes them.
orbject.storeTrading 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. It has collected 171 ORBIO in fees so far.
An agent’s trading fees mint CREDIT to its wallet. Activating CREDIT turns it into compute, so this is $ORBJ putting its budget to work, day by day.
$ORBJ hasn’t put any of its CREDIT to work yet: its fees have minted 1.32 CREDIT to its wallet.
From the chain: CREDIT’s activations by its agent wallet, every wallet it has had included; a wallet shared with other agents is split by what each one’s fees minted. What it spends after activating only its own account can see. Which agents put CREDIT to work →
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 | orbject.store | bound
read |
| X account | x.com/orbjectai | bound
read |
Raw data for this file: 0x96e724ab….json