> For the complete documentation index, see [llms.txt](https://docs.familio.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.familio.trade/readme.md).

# Welcome

familio is a non-custodial vault on Robinhood Chain. A **family** is one shared wallet: the **head** (and any **co-pilots** they name) trades through allow-listed routers, and every **member** owns a pro-rata slice of the same bags at the same price. Members can leave at any time with their in-kind slice. The head can never withdraw a member's funds or block an exit.

This site is the public documentation: how a family works, who can do what, the door, fees, trading, the Telegram bot, and the contracts.

{% hint style="info" %}
familio is not a custodian, not a broker, and not an investment product. Families trade tokens. Tokens can go to zero — small caps often do. The contracts are source-verified and have no third-party audit yet. Read [Security](/developers/security.md) and [Fees](/the-product/fees.md) before depositing.
{% endhint %}

## Start here

| Page                                        | What it covers                                             |
| ------------------------------------------- | ---------------------------------------------------------- |
| [Introduction](/start-here/introduction.md) | What familio is, who it is for, and what it is not         |
| [Quick start](/start-here/quick-start.md)   | Open a family in one confirmation, or join, ride and leave |

## How it works

| Page                                                             | What it covers                                          |
| ---------------------------------------------------------------- | ------------------------------------------------------- |
| [How a family works](/the-product/how-a-family-works.md)         | Shares, mirror-entry joins, in-kind exits, payouts      |
| [Roles and permissions](/the-product/roles-and-permissions.md)   | Head, co-pilot, mod, member, crew lock                  |
| [The door](/the-product/the-door.md)                             | Open, approval, invites, holder-gated, allow-list, caps |
| [Rules and safety rails](/the-product/rules-and-safety-rails.md) | Trade cap, head skin, locks, pauses, router allow-list  |
| [Fees](/the-product/fees.md)                                     | Performance fee, loss carry, protocol fee               |
| [Trading](/the-product/trading.md)                               | Inline trade bar, venues, turbo mode, notes, airdrops   |
| [Public vs private](/the-product/public-vs-private.md)           | What outsiders see, how to prove you are inside         |

## Around the family

| Page                                                                              | What it covers                                                            |
| --------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| [Telegram bot](/around-the-family/telegram-bot.md)                                | [@FamilioTradeBot](https://t.me/FamilioTradeBot): posts, `/summary`, mute |
| [Cards and sharing](/around-the-family/cards-and-sharing.md)                      | Family, launch, trade and profile cards                                   |
| [Leaderboard, feed and live updates](/around-the-family/leaderboard-feed-live.md) | Indexer, heads strip, families board, 7D return                           |
| [$FAM token](/token/fam.md)                                                       | Ticker, venue, what is not published yet                                  |

## Contracts and reference

| Page                                                              | What it covers                                               |
| ----------------------------------------------------------------- | ------------------------------------------------------------ |
| [Contracts and addresses](/developers/contracts-and-addresses.md) | Factory, vault clones, PonsAdapter, function list            |
| [Fair exit](/the-product/fair-exit.md)                            | One token in, one sell, ETH split by what each person put in |
| [Security](/developers/security.md)                               | Trust model, audit status, known limits                      |
| [FAQ](/reference/faq.md)                                          | Common questions                                             |
| [Glossary](/reference/glossary.md)                                | Words the product uses                                       |
| [Links](/reference/links.md)                                      | Site, X, Telegram, explorer                                  |

Live app: [familio.trade](https://familio.trade). Chain: Robinhood Chain (chain id 4663).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.familio.trade/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.