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

# Platform overview

21X operates an EU trading and settlement system for tokenized financial instruments. A trading pair has one orderbook on one blockchain.

Market View describes the pair; the orderbook matches and settles its orders.

* [**Explore the market data model**](https://docs.21x.eu/market-data/trading-pairs.md): Find the chain, contracts, scales, and trading status for a pair.
* [**Understand on-chain trading**](https://docs.21x.eu/trade-on-chain/order-model.md): See how orders are validated, matched, cancelled, and settled.

## Platform architecture <a href="#overview-components" id="overview-components"></a>

* Developer application
  * Market View REST API: GET requests return pair metadata and market snapshots.
  * Pair’s orderbook contract: Receives signed placements and cancellations. Emits order and trade events.
    * Base and quote token contracts: Transfer both assets together when a trade matches.

*The* [*read path*](https://docs.21x.eu/api-and-contract-reference/market-view-api.md) *identifies the network and address for the* [*write path*](https://docs.21x.eu/api-and-contract-reference/contract-interfaces.md)*. Each pair trades on one chain, Polygon or Stellar.*

## Execution and settlement <a href="#overview-execution" id="overview-execution"></a>

Secondary-market orders are placed and cancelled with signed blockchain transactions, not with REST requests. A match settles the instrument and payment legs together on-chain through atomic delivery versus payment (DvP).

21X supports [Polygon](https://docs.21x.eu/trade-on-chain/polygon.md) and [Stellar](https://docs.21x.eu/trade-on-chain/stellar.md). Follow `blockChain` and `orderBookVersion` on the selected pair; a listing does not execute across networks. Use [receipts and order events](https://docs.21x.eu/orders-and-settlement/order-lifecycle.md) to determine the outcome of an order, not whether it appears in a market snapshot.

## Related documentation <a href="#overview-related" id="overview-related"></a>

This reference explains the platform and its interfaces. Use the separate 21X Integration Guide for connectivity, sandbox setup, and implementation walkthroughs. See [Participant Docs](https://docs.21x.eu/participant-docs/getting-started) for venue roles and admission requirements.


---

# 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.21x.eu/platform/platform-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.
