$AGENTKIT Oak AgentKit
0x35e1951c0bd2d38d54249ddf3a534e13c2216a34
0x35e1951c0bd2d38d54249ddf3a534e13c2216a34
No. Not the token @oakagentkit claims (it claims $OAK 0x6511c23379…).
An official channel lists a different contract, or says this token isn't theirs.
Wrong verdict? Report it. A person reads every report, and it triggers a fresh check.
The onchain economy, open to your agent. One kit connects the Al you already use to swaps, prices, vaults and launches on Robinhood Chain.
The token description, written by whoever launched it.
Not scored
Impersonators aren't scored: nothing they point at belongs to them.
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. It has collected 208 ORBIO in fees so far.
An agent’s trading fees mint CREDIT to its wallet. Activating CREDIT turns it into compute, so this is $AGENTKIT putting its budget to work, day by day.
$AGENTKIT hasn’t put any of its CREDIT to work yet: its fees have minted 1.91 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? |
|---|---|---|
| X account | x.com/oakagentkit | contradicted
read |
Raw data for this file: 0x35e1951c….json