# Getting Started

Quantix Finance is designed as a modular credit infrastructure layer, enabling applications, institutions, and on-chain protocols to directly access programmable lending markets, structured yield, and capital-efficient borrowing.

Integration into Quantix is not constrained to a single pathway. The protocol supports multiple layers of interaction depending on the level of control, automation, and composability required. Whether the objective is to surface yield to end users, deploy capital programmatically, or build entirely new financial primitives, Quantix provides a unified framework for execution.

At its core, integration follows a simple principle: capital flows into structured credit pools, where it is allocated, monitored, and returned with yield based on predefined risk parameters. Everything else—interfaces, automation, and composability—is built around this foundation.

Developers and institutions begin by defining their role within the system:

* Are they routing capital into the protocol?
* Are they enabling users to access credit markets?
* Or are they building on top of Quantix as a financial base layer?

From there, integration is executed across three primary layers: frontend, backend, and smart contract level, each offering increasing levels of control and abstraction.

Quantix supports both permissioned environments for institutional participants and open market configurations for DeFi-native applications. This dual architecture allows integrations to align with compliance requirements while preserving the composability expected in decentralized systems.


---

# 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://quantixfinance.gitbook.io/quantixfinance-docs/integrate-quantix-finance/getting-started.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.
