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

# Application Layer

The Application Layer is responsible for turning financial infrastructure into usable financial experience.

Where the Asset Layer creates the base asset and the Financial Layer unlocks liquidity and financial functionality, the Application Layer makes the system accessible to end users. It is the point at which on-chain finance becomes practical, navigable, and relevant in everyday financial contexts.

This layer matters because a financial stack is incomplete if it remains accessible only to technically sophisticated users or specialized market participants. Real-asset finance reaches broader utility only when it can be used through simple, familiar, and application-driven interfaces.

Within Ontorium, the current flagship implementation of the Application Layer is **AQUA App**, a stablecoin-powered financial application for payments, transfers, and yield.


---

# 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.ontorium.io/ontorium-stack-overview/application-layer.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.