> For the complete documentation index, see [llms.txt](https://edexa-business-blockchain.gitbook.io/edexa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edexa-business-blockchain.gitbook.io/edexa-docs/basics/openapi.md). # edeXa Modular APIs Blockchain adoption in business has often been slowed down by complexity, rigid systems, costly integrations, and the need for specialized knowledge. edeXa changes that with **modular APIs**, designed like building blocks. Instead of rebuilding processes from scratch, companies can plug directly into blockchain functions, from identity and payments to data verification, in a way that fits their existing systems.\ \ This modular approach turns blockchain from a buzzword into a **practical tool for enterprises**, making adoption faster, cheaper, and future-proof. Businesses gain the freedom to start small, scale when ready, and stay competitive in an economy where trust, automation, and transparency are key. The following documentation outlines the **edeXa modular API services** currently available and connected to our **testnet and mainnet**, ready for businesses to explore and integrate. --- # 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://edexa-business-blockchain.gitbook.io/edexa-docs/basics/openapi.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.