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

# Abstract

<figure><img src="/files/BTyEGwBwriROonwdRnuV" alt=""><figcaption></figcaption></figure>

## Abstract

We are in an era of “super-individuals” ignited by artificial intelligence (AI). However, the production relations underpinning global collaboration—how we work, distribute, and settle value—have failed to keep pace with this transformation.

\
Boings was born to change this. **We are not just another token issuance platform. We are the first next-generation Quest Launchpad on BNB Chain**, dedicated to building a new work paradigm through integration with the 402 Open Payment Protocol: a bidirectionally efficient matching system for people and quests.

\
Under traditional corporate structures, a quest that could be completed in one hour is often delayed for a week due to rigid compensation systems. Boings will revolutionize this. Here, value will flow with unprecedented speed and precision to those who make truly creative contributions.


---

# 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://boingsai.gitbook.io/boingsai/abstract.md?ask=<question>&goal=<endgoal>
```

`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.