> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/whats-new/2025/september-2025.md). # September 2025 2025-09-26 ### Mapping Update We've identified some mapping discrepancies around instruments with the asset code NEIRO. This appears to originate from different exchanges using this same code to refer to at least 3 distinct assets. The mapping in our reference data will be updated as outlined below: `NEIROCTO` : First NEIRO on ETH\ `1NEIRO` : NEIRO ETH\ `NEIRO` : NEIRO 2025-09-23 ### Mapping Update * Instruments listed below are updated to use the base asset code `ONOMY` * CoinEx spot `nom-btc` becomes `onomy-btc` * Bitfinex spot `nom-usd` becomes `onomy-usd` & `nom-usdt` becomes `onomy-usdt` * KuCoin spot `nom-usdt` * MEXC spot `nom-usdt` --- # 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.kaiko.com/whats-new/2025/september-2025.md?ask=&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.