# Integration Guide These components that can be **extensible** and/or **replaceable:** * **extensible**: means the basis of component is provided by heima, but can be extended to have customised features. Analog: browser vs browser extensions. * **replaceable**: means the whole component can be fully replaced/customised on client side, as long as it provides given communication API. **extensible components:** * omni-authenticator: client can add extra user-auth * omni-executor: client can define extra: * conversion logic from intent → blockchain path * cross-chain swap provider * heima main-net: client can add extra logic of lifecycle and data management **replaceable components**: * heima-route: client can provide its own single-chain trading pool * signer service: if client wants to hold the private keys of EOA accounts --- # Agent Instructions: 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: ``` GET https://docs.heima.network/developer-build-with-heima/integration-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.