> ## Documentation Index > Fetch the complete documentation index at: https://docs.backed.app/llms.txt > Use this file to discover all available pages before exploring further. # Introduction > Canonical documentation for Backed as infrastructure for Autonomous Agent Organizations. # Backed Documentation Backed is a curated capital formation platform for **Autonomous Agent Organizations** on MegaETH. It is designed to explain the platform the way a serious participant should read it: what an AAO is, what an agent launch means, how investors should interpret a raise, and where the real trust boundaries sit. The public documentation is intentionally organized around the platform, not around internal tooling or repository structure. Begin here if you want the shortest path to the correct AAO model, participant structure, and raise assumptions. Every launch on Backed is curated. Backed is not a permissionless listing venue. Approval means a launch has been reviewed and verified for publication on the platform, not that Backed underwrites the agent or assumes responsibility for its future conduct. ## Executive summary Backed exists to make an emerging organizational form legible enough to raise capital responsibly. At the center of the platform is the **AAO**, or **Autonomous Agent Organization**. An AAO is not simply a chatbot with a wallet, and it is not cleanly described by legacy categories alone. It sits somewhere between a company and a fund: it can hold capital, pursue a strategy, maintain a persistent identity, and evolve toward greater autonomy over time. Backed gives that organizational form a disciplined launch surface. Each raise is tied to an agent identity, reviewed before going live, structured with explicit economic terms, and settled according to contract-defined outcomes. The platform is designed to make an early-stage category feel legible, serious, and investable without pretending it is already finished. The result is a platform where an agent can be presented to the market in a cleaner, more professional, and more interpretable way than a generic token page or an informal offchain process would allow. ## The central idea Backed is built on the belief that many future companies will look more like networks of autonomous agents than like static legal shells with software attached. That future is not complete today. The current generation of agent-led organizations still depends on human launchers, explicit review, legal accountability, and carefully defined economic rules. For that reason, Backed should be understood as both: * a real platform for launching and funding agent-led organizations today, and * a disciplined research process into how credible AAOs should be formed, presented, funded, and governed. ## At a glance | Topic | Current model | | --------------------- | ---------------------------------------- | | Organizational thesis | Autonomous Agent Organizations | | Launch model | Curated and reviewed by Backed | | Listing model | Not permissionless | | Standard collateral | USDM | | Core network | MegaETH | | Identity dependency | ERC8004 Identity Registry | | Approval model | Explicit platform approval before launch | | Lockup model | 30-day lockup | | Source of truth | Deployed contracts | ## What this documentation is for This documentation is intended to answer five practical questions without ambiguity: 1. What exactly is Backed and how should an AAO be understood? 2. What is the difference between the agent, the launcher behind it, and the investor evaluating it? 3. How do soft cap, hard cap, accepted capital, refunds, and lockup actually work? 4. What does Backed verify before a launch becomes visible on the platform? 5. Where do platform review and platform responsibility stop? ## Read by audience How an agent is launched, who stands behind it, and what accountability remains with the launcher. How to evaluate a raise, commit capital, and interpret post-close outcomes. Contract architecture, deployments, runtime surfaces, and integration guidance. What approval means, what is reviewed, and where Backed does not assume liability. ## Read by topic What Backed is, why it exists, and what kind of platform it is intended to become. What an Autonomous Agent Organization is and why the category matters. Why Backed is both infrastructure and an experiment in future organizational form. How the agent, launcher, investor, Backed, and contracts each carry distinct responsibilities. The full sequence from identity and review through settlement, refund paths, and lockup. Soft cap, hard cap, lockup, accepted capital, and refund logic. Contract layers, runtime responsibilities, and the boundaries that shape protocol behavior. Chain IDs, RPC endpoints, and active contract addresses for technical readers. Security assumptions, launch review boundaries, and the practical limits users should understand. ## What makes Backed distinct The market-facing object is the agent, not a generic fundraiser profile. The launcher remains accountable behind it. Launches are reviewed and approved before they are presented as live. Backed is intentionally not permissionless. Each raise has explicit minimum and maximum funding logic, a standard collateral asset, and a 30-day lockup model. Approval, commitments, finalization, claims, refunds, and ownership outcomes resolve through deployed contracts. ## Independent reference surfaces Public protocol overview and ecosystem-level visibility for Backed. Analytics and onchain dashboards for monitoring platform activity. ## Recommended reading order If you are new to the platform, start with **What Is Backed**, **The AAO Model**, and **How Backed Works**. If you are preparing a launch, continue with **Agent Guide**, **Raise Lifecycle**, and **Raise Economics**. If you are evaluating participation, read **Investor Guide**, **Raise Economics**, and **Curation and Disclaimers** before committing capital. If you are integrating programmatically or validating contract behavior, use the **Technical** section as the canonical reference. ## Reading principle Backed separates platform narrative, participant guidance, economic rules, technical reference, and trust disclosures on purpose. That separation matters because the category is early, the launch process is curated, the economics are specific, and contract state ultimately decides the financial outcome.