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

# Welcome to BagX

BagX is a revolutionary platform that allows Twitter/X users to **instantly tokenize their social capital** on Solana. Connect your Twitter account, and your personal token is created automatically, no technical knowledge required.

Built on top of the powerful [Bags API](https://bags.fm), BagX brings the future of social tokenization to everyone.

#### The Vision

> "Someone should build FriendTech on BagsAPI, use Privy and X login, launch a coin for every new user that joins"
>
> — [@finnbags](https://x.com/finnbags), CEO of Bags

That vision is now reality. **BagX is here.**

***

### Why BagX?

| Feature               | Description                                             |
| --------------------- | ------------------------------------------------------- |
| **Instant Launch**    | Your token is created the moment you connect Twitter    |
| **85% Revenue Share** | Earn 85% of ALL trading fees generated by your token    |
| **Instant Payouts**   | Claim your earnings anytime, paid in SOL                |
| **Secure Login**      | Powered by Privy - industry-leading Web3 authentication |
| **Solana Native**     | Fast, cheap, and scalable blockchain infrastructure     |


---

# 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.bagx.fun/welcome-to-bagx.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.