# Introduction

![](https://3875115089-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MTpZ7b3N-sEH07P7e_X%2Fuploads%2Fjrha7uU328BkdzBelakP%2FAURA-v3.png?alt=media\&token=068a6e7f-b370-4e95-b117-8343e302c0f4)

## What is our mission?

{% embed url="<https://youtu.be/xdxh3V7_DDA>" %}

$AURA is designed to disrupt the current browser industry by providing users with a brand new play-to-earn experience. \
\
Imagine starting an adventure with a brand new anonymous NFT avatar identity that levels up and generates rewards as you browse the internet. \
\
A new browser that is privacy-focused, shares advertising and transactional revenue with its userbase, incorporates all of the latest crypto, NFT, and DeFi technology while providing direct access into the Auraverse. \
\
Users will control decisions regarding company policy and community directives through a DAO governance system that ensures that power remains in the hands of the people.\
\
The way we browse the internet will never be the same again.


---

# 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://whitepaper.operationaura.com/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.
