> For the complete documentation index, see [llms.txt](https://docs.zert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zert.com/getting-started/readme.md).

# Introduction

ZERT is cross-chain swap infrastructure for wallets, exchanges, neobanks, and dApps. One integration gives your product access to 70+ chains, 900+ DEXs, and 6M+ liquidity pools through ZERT's routing and execution infrastructure.

ZERT scans live liquidity, ranks routes by real-world execution quality, stress-tests under simulated conditions, and executes privately — no MEV exposure, no front-running. Gas is covered by ZERT. Your users pay nothing extra.

ZERT is fully non-custodial. No KYC. No user accounts.

### Base URL

```
https://api.gateway.zert.com/api/v1
```

All public endpoints live under `/api/v1`. Authentication uses `Authorization: Bearer YOUR_API_KEY` on every endpoint except `GET /health`.

### Public Flow

The public swap flow is `Quote -> Build -> Sign -> Submit`:

1. `POST /quote`
2. `POST /swap/build`
3. `GET /swap/{swapId}/signing` until a signable payload is ready
4. Sign externally in the wallet or signer you control
5. `POST /swap/{swapId}/signing` with the signed artifact

Postman and GitBook help you inspect payloads and submit signed artifacts. They do not sign transactions.

### What's Next

| If you want to...                            | Go to                                                                                                        |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Get your API key and start calling endpoints | [Authentication & API Keys](/getting-started/authentication-and-api-keys.md)                                 |
| Do your first swap in 5 minutes              | [Quick Start — Your First Swap](/getting-started/quick-start-your-first-swap.md)                             |
| Walk through the full swap lifecycle         | [Guides → Full swap flow](/integration-example/full-swap-flow.md)                                            |
| Discover chains, tokens, and pairs           | [Guides → Discovery: chains, tokens, and pairs](/integration-example/discovery-and-quote.md)                 |
| Set up limit orders                          | [Guides → Limit orders](/integration-example/limit-orders.md)                                                |
| Track a transaction                          | [Guides → Check transaction status](/integration-example/check-transaction-status.md)                        |
| Explore all endpoints                        | [Zert API Docs](https://api.gateway.zert.com/docs)                                                           |
| See all data types                           | [ZERT APIs → Models](/models.md)                                                                             |
| Integrate with TypeScript                    | [Routing Engine SDK → Installation and Configuration](/routing-engine-sdk/installation-and-configuration.md) |
| Handle SDK and API errors                    | [Routing Engine SDK → Error Handling for APIs](/routing-engine-sdk/error-handling-for-apis.md)               |


---

# 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:

```
GET https://docs.zert.com/getting-started/readme.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.