> For the complete documentation index, see [llms.txt](https://haiko-docs.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://haiko-docs.gitbook.io/docs/info/listing-on-haiko.md).

# Listing on Haiko

## Permissionless listing

Haiko supports permissionless listing for non-strategy markets. You can create a new pool on the [Haiko Interface](/docs/info/user-guides/haiko-interface.md) simply by adding liquidity to the desired pair on the Positions page.

Initialising a new market requires setting the starting price of the market. We pre-fetch the market price of the token pair from Coingecko API, but leave it up to users to set the correct price.

## Whitelisting strategy

To protect its users, Haiko will initially operate under a whitelist for **strategy markets** and **owned markets**. 

These market types invoke hooks to inject custom external code into the AMM logic, meaning they are vulnerable to malicious attack. To prevent this, we require a manual review of all code for these market types.

## Requesting a whitelist

To request whitelisting for a strategy or owned market, drop us a message on [Discord](https://discord.gg/haiko-xyz).


---

# 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, and the optional `goal` query parameter:

```
GET https://haiko-docs.gitbook.io/docs/info/listing-on-haiko.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.