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

# Social

Social is how Koto turns trading into a shared experience. Users can follow market activity, share selected trades, react to posts, discuss ideas, and build smaller trading communities through friends and guilds.

## Business Purpose

Koto Social helps users discover context around markets and traders, not just prices. It makes trading activity easier to understand, discuss, and share while giving users control over who can see their posts and shared trades.

## Description

The Social experience is part of Koto's trading product. It sits alongside market activity so users can move between trading decisions and community context naturally. A user can browse public content, follow friend activity, participate in guild spaces, inspect profiles, and share their own trading moments when they choose.

Social content can include text posts, trade cards, shared posts, quote-style posts, guild activity, comments, replies, and reactions. The goal is to help users understand what others are watching or doing without forcing private trading details into public view.

## How It Works

1. Each logged-in user has a Koto social profile.
2. Users can browse feed activity based on audience and relationship: public, friends, guilds, or their own activity.
3. Users can create posts, react to posts, comment, reply, share posts, and quote posts where supported.
4. Users can add friends and use friend relationships to unlock friend-scoped content.
5. Users can create or join guilds to participate in group-level trading spaces.
6. When sharing a trade or post, users select the audience they want to reach where that control is available.

## What It Supports

* User profiles and profile previews.
* Public feed activity.
* Friend relationships and friend-scoped content.
* Guild spaces, guild members, guild requests, and guild-scoped posts.
* Posts, comments, replies, reactions, shares, and quote-style posts.
* Trade cards that summarize selected trading activity without making sensitive details public by default.
* Audience choices for posts and shared trades, including public, friends, guild, and private where supported.
* Notifications or prompts for social activity such as friend requests, guild invites, and post engagement where available.

## Social Details

### Feed

The feed is where users discover trader activity and conversations. Public content helps users see broad market discussion, friend-scoped content helps users follow people they know, and guild-scoped content keeps group conversations inside the relevant community.

### Profiles

Profiles give social activity a clear identity. A profile can help users recognize who posted, inspect relationship context, and decide whether to follow, add, or interact with another trader.

### Friends

Friends are direct social relationships. Friend status can affect what content a user can see and which actions are available. Friend-only content should only be visible to accepted friends where that audience is selected.

### Guilds

Guilds are shared spaces for trading communities. Users can use guilds to organize around a group, view guild-specific activity, and participate in posts or discussions intended for that guild.

### Audience Controls

Audience controls let users decide who should see a post or shared trade. Public content is for broad visibility. Friends content is for accepted friends. Guild content is for selected guild communities. Private content is for the user's own record where supported.

Social access depends on the viewer's relationship to the author, guild membership, and the audience selected for the post or shared trade.


---

# 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.pages.koto.trade/product/social.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.