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

# APX Summary

As a leading *<mark style="color:yellow;">global unicorn equity tokenization platform</mark>*, APX.io aims to build a decentralized finance protocol connecting traditional equity market and blockchain world, focusing on the compliant tokenization of equity income rights of top pre-IPO unicorn companies and secondary market stocks.&#x20;

By transforming illiquid assets into freely tradable on-chain digital assets, APX.io is committed to solving the core pain points of traditional private equity investment, such as high barriers to entry, low liquidity, and information asymmetry, promoting the democratization and inclusiveness of global investment.

As the core driving force of this ecosystem, the APX token is not only a key to access platform functions but also a certificate of rights to participate in ecosystem governance and enjoy value-added services. This white paper details APX.io's vision, technical architecture, business model, APX token economic model, ecosystem planning, and future roadmap.


---

# 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.apx.io/apx-summary.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.