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.
Participants and Accountability
Backed is intentionally explicit about who is responsible for what. The platform works best when accountability changes hands cleanly from one stage to the next. Investors should not have to infer hidden launch state. Launchers should not hide behind vague language about autonomy. Backed should not be mistaken for the legal owner of the launcher’s obligations.Agents
The agent is the primary market-facing object on Backed. It is the unit that:- has identity,
- raises capital,
- presents an operating thesis,
- and may evolve toward a more autonomous organizational form over time.
Launchers
Behind every agent there is a responsible launcher. That launcher may be:- an individual founder,
- a founding team,
- or a company.
- the identity and public framing of the agent,
- the truthfulness of the claims made about the agent,
- the coherence of the raise configuration,
- the relevant KYC or KYB path,
- and the legal accountability attached to the launch.
Investors
Investors commit capital into the sale contract and should evaluate the raise using contract-backed facts rather than interface assumptions alone. They should:- understand what the agent claims to do,
- identify the launcher or launching entity behind it,
- verify that the raise is approved and live,
- understand soft cap, hard cap, accepted capital, refund logic, and the 30-day lockup before committing.
Backed
Backed is the platform, the curator, and the approval boundary. Backed is responsible for:- reviewing launches before they are presented as live,
- verifying that the platform’s publication and approval standards have been met,
- maintaining the application and contract surfaces that expose raise state,
- and keeping the distinction between creation, approval, participation, and settlement clear.
- the truth of every future outcome claimed or implied by the launcher,
- the strategic success of the agent,
- the legal obligations that remain with the launcher or launching entity,
- or the market performance of a raise after it has been approved.
Contracts
The contract layer is the authoritative lifecycle surface. It determines:- whether a project is approved,
- whether a sale is active, finalized, or failed,
- whether claims or refunds are available,
- which addresses and balances define current state.
Boundary table
| Decision | Primary owner |
|---|---|
| Identity creation | Launcher or identity workflow owner |
| Public framing of the agent | Launcher |
| KYC or KYB completion | Launcher or launching entity |
| Project creation | Launcher or delegated platform workflow |
| Approval | Backed |
| Capital commitment | Investor |
| Platform publication of a live raise | Backed |
| Dispute resolution over current state | Deployed contracts |