# Introduction

Here at Busdy we like to keep it real. Our motto...

> No BS.
>
> Just USDC, $BADDIES, and Bullish Meme-tility!&#x20;

We are here to be different. We are here to make a statement; to be beautifully simplistic, and effortlessly enchanting.&#x20;

Acknowledging the likelihood of an upcoming bear market, we wanted to give investors something that would be most valuable to them. Our conclusion, stable coins. USDC in specific. So, we decided to develop a token with generously high USDC rewards.

Next, the name. It had to be perfect. We debated name after name until finally stumbling upon Busdy, a witty play-on-words of "Busty." &#x20;

Finally, the branding. More than just the carnal images that flow into mind when one thinks of the word, we needed a brand that would appeal to global audiences. This one was easy. Anime. A recognizable artistic style with international popularity.&#x20;

![](https://1934066772-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJm6YRapSVtu7GwbsH7NB%2Fuploads%2FJKTsEHmWISuiNSMCo3bE%2FMASTERBUSDYLOGOMASTER%20clearBG%20\(1\).png?alt=media\&token=6a345c63-78da-47c7-b7df-d87e4f6cf24c)


---

# Agent Instructions: 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://busdybsc.gitbook.io/usdbusdy-whitepaper/introduction.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.
