> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/readme/compatibility.md). # Compatibility Whether it’s an in-house development or a ready-made standard solution, FactFinder can be integrated into any shop. With our API-first approach, any programming language can query FactFinder and return all the data you need to display to your customers. The logic behind which results are shown — and how — can be easily managed in our intuitive Management UI. From consulting and implementation to after-sales support, our FactFinder team is at your side every step of our collaboration. Our platform comprises a comprehensive suite of modules that deliver results for any use case, providing the tools shoppers need to find what they are looking for and giving business users the ability to create bespoke discovery experiences that stand out from the competition. ![Compatibility overview](/files/qfrgJiMODjM8BqowIJGw) Read more on how to integrate FactFinder here: [Integration](https://docs.fact-finder.com/integration/) ![FactFinder NG compatibility diagram](/files/hpUBLhVHEdsSokVVNgFc) --- # 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://docs.fact-finder.com/docs/readme/compatibility.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.