> 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/partners-flow/partners.md).

# Partners

Discover the Partner Library as a partner.

As a partner of Emporix, you can use the Partner Library to extend your offering and turn the integrations or workflows you create into products discoverable directly within the Emporix ACE<sup>™</sup> platform. This way you build your profile of trust and safety. The Partner Library is where customers can find your components and easily decide to adopt them.

You can sell the following components in the Partner Library:

* **Extensions** - An extension is an add-on functionality that extends Emporix platform (integrations, payments, tax, shipping, B2B modules, and more) and is visible within the Emporix Management Dashboard as a node or as a perspective. An extension typically includes versioning, compatibility, permissions/scopes, APIs/events/webhooks, and updates.
* **Value Streams** - Packaging of repeatable business process automations or workflow blueprints (for example, returns handling setup, fraud workflows, catalog enrichment processes, and more).
* **AI Agents** - Predefined AI Agents to automate and streamline processes with or without humans in the loop.
* **Cloud functions** - Serverless services that allow you to run custom code and enable custom logic in response to events in the system. Cloud functions serving specific purposes offer a lightweight method to connect system events with external cloud services and perform specific tasks.


---

# 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/partners-flow/partners.md?ask=<question>&goal=<user_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.