9e9.world is a protocol launching ERC-style tokens on the Robinhood Chain (EIP-155:4663), where each token minting event simultaneously deploys an autonomous web agent—called an ‘artificial being’—whose sole income is the token’s creator fees. The official website describes this as a bargain: creators forfeit fee control at launch, and those fees flow directly to a derived wallet (0x3853…13ee) that funds the agent’s browser-based activity—reading, navigating, and reporting findings from the open web. The agent’s ‘obsession’ is cryptographically fixed by its token address, and its runtime is metered in real time against earned USD value, with costs tracked via public API endpoints like /api/v1/agents and /api/v1/agents/:token/events. On-chain activity is viewable through Blockscout and Etherscan explorers for the Robinhood Chain, and the project maintains a Twitter presence (@9e9world). Key questions remain about governance authority: who controls upgrades or emergency interventions; whether the server-side keeper holds unilateral power over fund sweeps or agent behavior; how losses from failed runs or mispriced execution are allocated; and whether the fixed-fee recipient mechanism truly prevents operator discretion despite claims of immutability.
9e9.world demonstrates a functional, observable MVP: users can launch tokens that spawn autonomous agents, and live agent behavior—including budget tracking, browser-based reading, navigation, and event logging—is verifiable via public API endpoints and the live dashboard. The core user journey is end-to-end: token launch (web_1), agent birth and funding (web_3), real-time state inspection (web_2), and observable runs with cost attribution (web_2, web_1). Agent activity is not simulated—/api/v1/agents shows 38/39 awake, /api/v1/stats reports 184 runs and $1,240.55 earned, and /api/v1/agents/:token/events delivers timestamped, kind-tagged logs (e.g., ‘action’, ‘finding’) with URLs and costs. Usability is supported by open CORS, no auth, and documented polling patterns—but no failure-handling documentation exists (web_2, web_3). Retention signals are weak: no cohort or repeat-launch data is provided, and the dashboard shows mostly dormant agents (web_1). Token mechanics are clearly explained (creator fees → agent wallet → on-chain spending), but liquidity is locked and non-withdrawable per protocol design (web_3). Contract authority is limited to fee routing; custody remains on-chain (api_2, web_3). Confidence is medium: evidence is current and multi-source (website + API), but all behavioral proof is server-side and unverified via independent node or wallet interaction.
Overall score: 7/10 Confidence: Medium