> 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-fallback-layer.md).

# The Fallback Layer

### Introduction

The Fallback Layer is where orders are executed through external AMMs when off-market fulfillment is unavailable. Acting as Gradient’s safety net, this layer ensures no trade is left unfilled.

When neither the Flash Layer nor the Matching Layer can fulfill an order within the user’s defined parameters, Gradient’s CORE automatically routes the trade through the most favorable AMM — aggregating across platforms to secure the best available price.

This guarantees complete trade execution with minimal friction, preserving intent while maintaining flexibility and price efficiency.

### Fallback Aggregation Logic

Gradient’s Fallback Layer functions as a built-in aggregator, scanning across AMMs in real time to identify the most favourable execution path.

* Route Optimization: Gradient's fallback system intelligently evaluates all available routing paths in real time, factoring in token pricing, gas costs, volatility, and liquidity distribution
* Multi-AMM Liquidity Sourcing: Gradient’s fallback system aggregates liquidity from multiple AMMs to reduce fragmentation and widen access to capital.
* Intent Respecting: Trades are only executed if they meet the user’s original parameters for price and volatility.

This layer ensures that Gradient captures every execution opportunity, without compromising control or pricing integrity.


---

# 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-fallback-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.