> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/partner-library/readme.md). # Partner Library Partner Library serves as a marketplace of components such as extensions, Value Streams, and AI Agents. Partners sell components, customers buy and could adopt them. The Emporix Partner Library is a curated marketplace within the ACE^™ platform that connects Emporix partners with Emporix customers. It's a destination where you can discover and adopt verified extensions, Value Streams, and AI Agents that extend the Emporix ACE^™ platform. By combining selected listings, compatibility guidance, and clear support ownership, it brings benefits to both partners and customers. As a **Partner**, you are enabled to share your expertise directly with customers as you can offer the components you've built for Emporix use cases to a broader audience. The Partner Library provides a standardized, secure and scalable way to commercialize your solutions. As a **Customer**, you can discover what's already prepared and validate that against your needs to reduce implementation effort and time-to-value, or extend your commerce capabilities with minimal friction.


Introduction	Get familiar with how the Partner Library can support your business goals.	Introduction
Partners Flow	If you are an Emporix Partner, learn how you can commercialize your components.	Partners
Customers Flow	If you are a Customer, learn how you can accelerate implementation of your e-commerce solution with prebuilt components.	Customers

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.emporix.io/partner-library/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.