> 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/around-the-family/cards-and-sharing.md).

# Cards and sharing

Every shareable object on familio is a 1200×630 card that reads without the page around it. Open Graph and Twitter `summary_large_image` use the same images. On X, the share button copies the link plus a one-line caption; the card is what the embed shows.

## Family card

`/api/og/family/<slug>` — avatar, name, head, 7D number, value in the vault, members riding, fee. Used on `/f/<handle>`, the explore grid, and **Manage → social → share the family**.

The URL is keyed on the figures it prints (7D, member count, value, paid out), so a new number is a new image and an unchanged one stays cached.

Private family, outsider: a generic **private family** card (face, name, head). No numbers.

## Launch card

Rendered the moment the create transaction confirms (`/api/og/launch?name&slug&kind&fee&mode`). "Just opened", picture, kind, door mode, fee, day 1. Share it from the success screen before the indexer has even caught the first block.

## Trade cards

`/api/og/trade/<slug>/<id>` — the receipt behind `/t/<slug>/<id>`. Buy or sell, token, size, realised, note if there was one. Share from the feed or from the latest-trade button in the social tab.

## Head profile cards

`/api/og/u/<handle>` — `/u/<handle>`. The head's face, handle, families they run. A **verified** X or Telegram @ on the profile (green checkmark) means that platform confirmed the link via OAuth or Telegram login — not an endorsement, just proof it is really theirs.

## Other cards

| Card      | Route                      | Use                                                                                        |
| --------- | -------------------------- | ------------------------------------------------------------------------------------------ |
| Slice     | `/api/og/slice/<slug>`     | "My slice of X · ±% · y% of the vault" from `/me`                                          |
| Invite    | `/api/og/invite/<slug>`    | `/join/<code>` landing                                                                     |
| Milestone | `/api/og/milestone/<slug>` | Feed milestones (crew, fee change, door change)                                            |
| Board     | `/api/og/board`            | Leaderboard snapshot — heads strip and/or families board (7D / 30D / all / paid / members) |
| Site      | `/api/og/site`             | Default site embed                                                                         |

## @handles on cards

A wallet is a hex string until someone puts an @ on it.

* A **familio profile** handle (`/u/<handle>`) is the default name for that wallet everywhere.
* The head can also pin a **Telegram or X @** on each crew wallet (create wizard, or the crew card on the door) so members recognise who is at the wheel even if that co-pilot has no familio profile. Those labels are per family, off-chain, and show next to the crew on the page, on cards, and in `/summary`.

## X share

The share control copies `https://familio.trade/…` and a caption (family name, head @, 7D, member count, or the latest trade). It does not auto-tweet. Paste into X yourself. Private families still produce a link; the embed stays the generic private card for anyone who is not inside.

Connect X from the head panel if you want the public X handle stored on the family's identity (identity tab). That is a profile field, not a posting integration.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.familio.trade/around-the-family/cards-and-sharing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.