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

# TL\*DR

Sunny is a campaign engine built for creators and brands.\
\
Developed by Web3 marketers in collaboration with Biobots, an AI and virtual fashion studio, Sunny focuses on user-generated content (UGC) and turns it into real, verifiable rewards. It bridges Web2 and Web3 with smart incentives, clear rules, and transparent payouts, always powered by the $SUNNY token as a direct utility layer for campaigns.

The system is plug-and-play, whether for PR pushes, meme campaigns, affiliate activations, or X-based engagements. Integrated with Bankr, Sunny automates onchain payments and tracking. Its tools include pHash for content validation and fair tipping, ensuring originality is rewarded.\
\
Sunny is the first mover combining automation, the creator economy, and socialFi infrastructure. By running campaigns on Sunny’s Terminal, $SUNNY tokens are circulating providing utility and value through the value chain of creators and brands.


---

# 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:

```
GET https://sunnyagent-ia.gitbook.io/sunnyagent.ia-docs/tl-dr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.