> For the complete documentation index, see [llms.txt](https://yape-club.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yape-club.gitbook.io/docs/readme.md).
# Welcome to Yape Club
The Smart Social Layer is Yape Club’s engine for coordinated, high-quality engagement between Web3 smart creators.\
\
It helps creators grow influence on X by surfacing high-value accounts, matching them through content clusters, account quality, and audience overlap, and rewarding meaningful engagement.
Yape builds a smart, curated, and reputation-weighted engagement layer. It organizes creators into fair-value engagement loops, where your influence and actions matter.
### Who It’s For
Yape’s Smart Social Layer is built for:
* InfoFi natives: users of Kaito, Cookie, Wallchain, and other InfoFi platforms.
* Mid-tier creators: accounts that create useful, high-quality content but are stuck at the same level of reach and X Score
* Builders & Analysts: people who care about the *quality* of their audience (smart followers) rather than vanity metrics.
### Who is Yape?
**Yape** is the hyperactive mascot and AI agent of Yape.Club. He lives in the feed as your co-author and navigator, helping yappers craft content that cuts through the noise and guiding them toward high-value engagement within the InfoFi ecosystem.
More than just a meme, Yape personifies the smart engagement engine itself, turning scattered, inefficient yapping into a structured, scalable system for attention. He represents the shift from chaotic posting to strategic communication, helping users grow their X scores, mindshare, and influence in a transparent and fair environment.
---
# 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://yape-club.gitbook.io/docs/readme.md?ask=&goal=
```
`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.