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

# WHAT IS PHT

- [PHT Overview](https://docs.apacx.io/what-is-pht/pht-overview.md)
- [Competitive Advantages](https://docs.apacx.io/what-is-pht/competitive-advantages.md): PHT offers a compelling proposition in the evolving world of digital currencies, thanks to its unique features and strategic focus. Below are the key competitive advantages that set PHT apart:
- [Multi-Collateral System](https://docs.apacx.io/what-is-pht/multi-collateral-system.md): PHT utilizes an over-collateralization model inspired by DAI, a proven and stable mechanism that has demonstrated resilience, particularly during market turbulence.
- [Stability and Yield](https://docs.apacx.io/what-is-pht/stability-and-yield.md): The APACX Protocol uses a Stability Fee mechanism to maintain the PHT peg to PHP while ensuring system reserves remain robust.
- [Risk Management](https://docs.apacx.io/what-is-pht/risk-management.md): APACX Protocol is designed to be robust and secure, yet like any innovative system, it faces inherent risks. We proactively address these risks through multiple layers of safeguards and mornitoring.
- [Product Roadmap](https://docs.apacx.io/what-is-pht/product-roadmap.md)


---

# 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://docs.apacx.io/what-is-pht.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.