> For the complete documentation index, see [llms.txt](https://winzyai.gitbook.io/winzyai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://winzyai.gitbook.io/winzyai/readme/what-problem-does-winzyai-solve.md).
# 🧩 What Problem Does WinzyAI Solve?
Despite massive growth in AI and Web3, most people are still consumers — not creators or earners. Existing platforms either require technical skills, are hard to monetize, or lack a fun, community-driven experience.
\
**WinzyAI solves this by:**
* Letting anyone **create AI agents** with no coding or setup complexity
* Embedding AI into **daily games, quizzes, and social challenges**
* Making it easy for users to **earn from their creativity and engagement**
* Simplifying crypto onboarding with Telegram-native access and **instant play**
It removes the barrier between **curiosity and income**, allowing users to become builders, entertainers, and earners instantly.
---
# 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://winzyai.gitbook.io/winzyai/readme/what-problem-does-winzyai-solve.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.