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

# The CORE

### Introduction

Gradient’s core innovation is its Coordinated Order Routing Engine, a native, off-chain engine designed to match token trades efficiently and transparently before on-chain execution.

With a focus on efficient, constraint-bound order matching, Gradient's CORE matches buyers and sellers with Market Makers and each other, completing transactions off-market in real time at preferred rates.

This system allows users to bypass traditional AMMs when counterparties are available, eliminating price impact & slippage and improving capital efficiency.

### Off-Market Order Matching

Unlike traditional AMMs and fragmented DEX liquidity, Gradient's CORE operates off-market. This allows orders to be matched in a secure, controlled, and private environment. This means:

* Orders are never exposed to front-running.
* Orders are never affected by slippage or price impact.
* Matching is handled off-chain for real-time efficiency.

Orders are submitted with predefined parameters, such as:

* Token pair
* Price limits
* Order size
* Time-to-live (TTL)

CORE continuously scans the order book to identify valid matches between buyers, sellers, and market makers, before sending a single, automatic settlement transaction on-chain.

### On-Chain Settlement

Once a match— either via Market Makers or P2P— is confirmed off-chain, CORE triggers a secure, on-chain settlement.

* Funds are transferred automatically.
* Trade details remain on-chain.
* Users retain custody until execution, minimizing risk.

This hybrid approach combines off-chain speed with on-chain trust.


---

# 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.gradient.trade/how-it-works/the-core.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.