# Introduction

⚠️ <mark style="color:$danger;">Internal Use Only - Not For External Distribution</mark>

Lynx is a fully on-chain decentralized exchange. All trading state is on-chain and verifiable against the State Root. This determines a fundamentally different API design from a traditional CEX:

* **Public reads** — All on-chain state (orders, positions, balances, executions) is queryable by anyone without authentication.
* **Signed writes** — All state changes are submitted as signed transactions and verified on-chain by node-side ECDSA validation.
* **No custodial keys** — The platform never holds your private key. You authorize API trading through an Agent Key.

Reference architecture: Hyperliquid (signed-transaction model, Agent Key) + Bybit / Kraken (RESTful routing, clean API documentation structure).

## Endpoints

| Category  | Method | Base URL                      | Responsibility                                                                                     |
| --------- | ------ | ----------------------------- | -------------------------------------------------------------------------------------------------- |
| Writes    | `POST` | `http://10.34.8.77:8481/v1/*` | Signed transaction submission. All write operations use `POST`; the path identifies the operation. |
| Queries   | `GET`  | `http://10.34.8.77:8481/v1/*` | Public read operations, no authentication.                                                         |
| WebSocket | WS     | `ws://10.34.8.77:8481/v1`     | Real-time push (public + user channels, subscribed by address).                                    |


---

# Agent Instructions: 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.lynxtrade.world/introduction.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.