> 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/gradients-layers/the-matching-layer.md).

# The Matching Layer

### Introduction

The Matching Layer is where orders are fulfilled via dynamic peer-matching. This is Gradient’s most flexible execution layer for both buy-side and sell-side participants.

Gradient's matching layer affords users full control over the execution terms of their trade, allowing them to set their own pricing, timing & volatility parameters.

Orders are automatically fulfilled fully or partially depending on the counterparties available, with Gradient's CORE ensuring precise and constraint-respecting execution.

### FIFO Fulfillment Logic

Gradient's CORE enforces a First In, First Out (FIFO) policy for all peer-matched orders. This guarantees:

* Fairness: Earliest orders are prioritized.
* Efficient Liquidity Management: Large orders don't decelerate existing order fulfillment.
* Transparent Execution Sequence: This allows for strategic and predictable order placement.

FIFO applies to all trades fulfilled via the Matching Layer, providing predictability for users submitting large or time-sensitive orders.


---

# 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/gradients-layers/the-matching-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.