> 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/changelog/in-progress/in-progress.md).

# Current work in progress

See what we are currently working on.

You can expect some changes in the nearest future regarding the workings of the mentioned services.

{% hint style="warning" %}
These announcements are intended to keep you informed about ongoing work and potential updates to the Emporix services. They do not guarantee new functionality. Please note that these updates are subject to change. Our goal is to provide you with this information so that you can consider it in your implementation and enablement plans.
{% endhint %}

| Service Name          | Description                                |
| --------------------- | ------------------------------------------ |
| B2B Commerce Frontend | Optimization of coupon and segment support |
| Schema Service        | Site awareness of mixins                   |
| Vendor Management     | Vendor-specific coupons                    |
| Customer Segments     | Group-aware customer segments              |
| Agentic               | Generic MCP                                |


---

# 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://developer.emporix.io/changelog/in-progress/in-progress.md?ask=<question>&goal=<endgoal>
```

`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.