> For the complete documentation index, see [llms.txt](https://help.rhinonature.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhinonature.com/api/integrations.md). # Integrations ## Overview A summary of a simple yet robust solution to connect Rhino Nature with your application. ## Link The Rhino Nature Bridge namespace exposes the Link class that provides a set of methods allowing for seamless communication for managed as well as unmanaged code. It is meant to bypass complex Rhino internal structures and focus on the most important elements usable on both ends. In addition to that, it allows performing live updates whenever new data arrives. The most typical use case is communication between Rhino Nature and a rendering engine. The advantage of this solution is giving your user the ability to render millions of objects using your own instancing routines without overloading system resources as well as the host application. In both cases, managed and unmanaged, it is prepared wisely not to collide with various policies without the need of using external third-party dependencies during the compilation. Communication is done via COM object available to anyone at runtime. There are available header and example files that will boil your work down to the bare minimum, hooking wires to appropriate places. Those are supplied along with the installer and are located under the API subfolder in the installation directory. If you need assistance during integration don't hesitate to drop an email at [support@rhinonature.com](mailto:%20support@rhinonature.com). --- # 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://help.rhinonature.com/api/integrations.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.