> For the complete documentation index, see [llms.txt](https://axiology.gitbook.io/axiology-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://axiology.gitbook.io/axiology-docs/getting-started.md). # Getting Started ### Testing Environment Before a participant can start working on technical integration, he must agree with Axiology and receive access to Testing Environment. This environment will include: * Several bonds or equities depending on your needs from Axiology * One EMT token for testing (currency object) * Several investor type wallets for testing * API to access features of testing environment Together with environment, participant will receive support from Axiology tech team during the process of API features integration. ### Requirements Before the beginning of integration there are several prerequisites that must be had: * A node in testing environment of Axiology * An existing (or new) system written in a chosen programming language, into which Axiology API is going to be integrated * An API testing tool (such as Postman or Insomnia) to experiment with requests and inspect responses during integration development. --- # 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://axiology.gitbook.io/axiology-docs/getting-started.md?ask=&goal= ``` `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.