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

# Overview

LiquidCore is an oracle-validated AMM live on HyperEVM and Robinhood Chain. It provides deep, liquid markets with predictable execution and tight spreads.

Ready to integrate? Start with the [Integration Guide](/liquidcore-integration/integration-guide.md).

## Supported chains

| Chain           | `chainId` | Router                                       |
| --------------- | --------- | -------------------------------------------- |
| HyperEVM        | `999`     | `0x625aC1D165c776121A52ff158e76e3544B4a0b8B` |
| Robinhood Chain | `4663`    | `0x322F277BfB7Ba9c196194ad18011377A0fF55Fb3` |

On HyperEVM, pricing uses Hyperliquid precompiles. Prefer the `routerAddress` returned by the [quote API](/liquidcore-integration/api-endpoints.md#get-quote) when executing.

## Pools

Do not hardcode pool addresses — they differ by chain and change over time. List pools from the API:

```
GET https://api.liqd.ag/liquidcore/pools?chainId=999
GET https://api.liqd.ag/liquidcore/pools?chainId=4663
```

Each entry includes `poolAddress`, token metadata, reserves, fees, volume, and APR. Full response shape is in the [REST API](/liquidcore-integration/api-endpoints.md#list-pools) reference.

For swaps, use the **router** — it discovers the correct pool automatically, so your integration does not need to track pool addresses.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.liqd.ag/liquidcore-integration/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.