> For the complete documentation index, see [llms.txt](https://metya.gitbook.io/metya/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metya.gitbook.io/metya/vision-and-narrative.md). # Vision & Narrative SocialFi alone creates “earnable” value but lacks spend scenarios; payments alone deliver “spendable” power but lack growth via relationships. PayFi + SocialFi fuses both: social behavior becomes a measurable asset (interactions, reputation, content, follower graph), and payments convert that asset into immediately redeemable value (membership, boosts, tipping, offline purchases, merchant perks). In short: social = asset; payment = value—the former creates value and stickiness; the latter validates and recirculates it. Coupled together, users no longer stay only for “rewards,” but for experiences they can spend on and want to spend on, making retention natural and compounding growth driven by high-frequency consumption. --- # 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://metya.gitbook.io/metya/vision-and-narrative.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.