> For the complete documentation index, see [llms.txt](https://docs.apex-ai.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apex-ai.ai/appendix/usdapex-token-utility.md).

# $APEX Token Utility

The **$APEX token** is designed with real, sustained utility at the heart of Apex AI’s mission: improving early detection of gastrointestinal (GI) cancers through AI-driven diagnostics.

#### 1. Driving Real-World Adoption

* Apex AI’s web platform enables anyone to securely upload endoscopic images and receive AI-powered diagnostic insights with **95%+ accuracy**, surpassing human specialists (\~70%).
* Each diagnostic transaction creates real demand, linking healthcare usage directly to the token economy.

#### 2. $APEX Flywheel

* Users who's local hospitals don't have access to Apex AI can pay for diagnostic reports on Apex Ai's web platform using **credit/debit cards.**
* A portion of the platform’s profits are allocated to **buy back and burn $APEX tokens**.

#### 3. Global Market Potential

* With \~250M endoscopies performed annually worldwide (\~20M in the U.S.), the addressable market is massive.
* As the platform scales globally, token buybacks will grow in parallel—directly rewarding long-term holders.

#### 4. Beyond Diagnostics: Internet Capital Markets (ICM)

* $APEX also plays a role in **Phase 2 of Internet Capital Markets**, bridging healthcare innovation with Web3 finance.
* $APEX holders can gain **exclusive access** to Apex AI funding rounds via SPVs managed by D-Day.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apex-ai.ai/appendix/usdapex-token-utility.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
