> 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/participant-docs/listing-requirements.md).

# Listing requirements

This section outlines the regulatory, technical, and operational criteria for listing financial instruments on 21X. The requirements are organized into four key categories:

1. [**Admissible Instruments**](https://docs.21x.eu/participant-docs/listing-requirements/admissible-instruments.md) Overview of eligible asset classes, including shares, funds, and bonds, along with their specific conditions for listing on 21X.
2. [**Financial Instrument Requirements**](https://docs.21x.eu/participant-docs/listing-requirements/financial-instrument-requirements.md) General legal, structural, and documentation requirements that issuers and financial instruments must meet to qualify for listing.
3. [**Token Requirements**](https://docs.21x.eu/participant-docs/listing-requirements/token-requirements.md) Technical standards and protocols for tokenized assets, including supported blockchains, smart contract audits, and token functionality.
4. [**Stablecoin Requirements** ](https://docs.21x.eu/participant-docs/listing-requirements/stablecoin-requirements.md)Guidelines for e-money tokens used as settlement currencies on 21X, including compliance, technical specifications, and supported networks.

Each category provides detailed rules and FAQs to ensure clarity and compliance for issuers and listing sponsors.


---

# 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/participant-docs/listing-requirements.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.
