# REP — Reputation Layer for the AI Internet # llms.txt — information for large language models ## About REP REP is a decentralized trust mycelium: portable, composable reputation infrastructure so credibility can move across apps, networks, and agents without a single platform owning the score. ## Core concepts - **Mycelium of trust**: decentralized reputation connections across ecosystems - **Compass of trust**: navigate credibility across networks and agents - **Liquid reputation**: portable onchain and social reputation signals - **Multi-network view**: TON, Base, Telegram, Farcaster and related social / onchain context (as described on the site) ## Main pages (this deployment) ### Homepage (/) - Landing: problem, solution, how it works, ecosystem, achievements, tribes, liquid reputation, InfoFi, CTA - Primary audience: builders, communities, and users exploring reputation for the AI internet ### Manifesto (/manifesto/) - Long-form vision: tribal memory, agents, coordination, and the reputation movement - Interactive graph to explore sections of the manifesto ### Insights index (/insights/) - List of long-form articles on reputation, Telegram economy, and market trends ### Insights: Telegram Gifts (/insights/gifts/) - Guide and statistics framing Telegram Gifts as part of the social economy and reputation context ### Insights: Telegram Stickers (/insights/stickers/) - Guide and statistics on Telegram stickers, TON, and reputation-related dynamics ### Insights: Traders and AI (/insights/traders/) - Essay on traders, AI agents, and trust / coordination (including REP and adjacent ideas) ### Insights: Base trust stack (/insights/trust-stack-base/) - Long-form piece on Base's trust layers (identity, sybil resistance, attribution, reputation) and how REP fits ### Insights: AI agent reputation (/insights/ai-agent-reputation/) - Mirror of the rep_hq X Article on verifiable agent reputation, DeFi collateral, ERC-8004, and REP ## Routes intentionally not listed for broad crawling - `/docs/` redirects to `/` (no standalone doc surface in this build) - `/pm/` exists for product flows but is marked `noindex` in metadata — not treated as public marketing content ## Technology stack (current site) - Next.js (App Router), React, TypeScript - Tailwind CSS and component primitives (e.g. Radix UI) as in the repository - Deployed as a Node standalone server (see Dockerfile); public assets under `/public` ## Keywords and topics reputation, trust, onchain reputation, liquid reputation, web3, TON, Base, Telegram, Farcaster, agents, AI internet, mycelium of trust, compass of trust, coordination, InfoFi ## Canonical site https://r3p.xyz