Install Jentic One Beta

Connect the Mx.Web.WebAPIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mx.Web.WebAPIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmxdev.mobile%2Fmxdev" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmxdev.mobile%2Fmxdev" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mx.Web.WebAPIs API.

Record a production BOM make, with BOMMakeDetail lines of ItemCode, Quantity, UOM, and TransactionTime, against a StoreNumber through POST /External/Inventory/Webhook/

Send a stock transfer between stores with FromStoreNumber, ToStoreNumber, a TransferType of Sent or Request, and Items with BoxQty and InnerQty

Log waste with WasteDetail lines carrying a WasteType of InventoryWaste or FinishedWaste, a WasteReason, and a ProductionBOMWasteMethod

Post back-of-house inventory counts, purchase orders, transfers, waste, credit memos, or BOM makes through POST /External/QuBeyond/WebhookAnonymous

GET STARTED

Start building with Mx.Web.WebAPIs API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mx.Web.WebAPIs API for, with concrete tasks.

★ Kitchen systems feeding Macromatix through Jentic

An agent that sits between kitchen production tools and the Macromatix back office can push each batch as it happens. Through Jentic it finds the External Inventory webhook by intent and posts a production BOM event with the StoreNumber and BOMMakeDetail lines of ItemCode, Quantity, UOM, and TransactionTime. When the response lists entries in InvalidRecordIndex, the agent reports the failing lines and their Messages instead of silently dropping them.

Call POST /External/Inventory/Webhook/ with type 'pret.kitchen.ProductionBOMMake.published' and Data containing StoreNumber '251' and one BOMMakeDetail line with ItemCode 'PBMSANDWICH01', Quantity 20, UOM 'Each', and TransactionTime '2026-11-09T09:00:00Z', then report any InvalidRecordIndex entries

Store-to-store stock transfers

Hub-and-spoke kitchens move stock between sites during the day. The Transfer event carries an ExternalReference, a TransferType of Sent or Request, FromStoreNumber and ToStoreNumber, a TransferDate, optional fresh and frozen temperatures at the sending store, a Comment, and Items with BoxQty and InnerQty per ItemCode, so each movement lands in Macromatix with the detail needed to reconcile both stores.

Call POST /External/Inventory/Webhook/ with a Transfer event whose ExternalReference is 'TRF-20261109-001', TransferType 'Sent', FromStoreNumber 'HUB001', ToStoreNumber 'SPOKE015', and Items with ItemCode 'BREAD-001' and BoxQty 2

Waste logging with reasons

Waste data is only useful when the reason and method are recorded. Each WasteDetail line takes an ItemCode, Quantity, UOM, and TransactionTime, a WasteType of InventoryWaste or FinishedWaste, a free-text WasteReason, and a ProductionBOMWasteMethod of MakeAndWaste, WasteAsIngredients, or WasteOnly, which tells Macromatix how to treat the item's ingredients.

Call POST /External/Inventory/Webhook/ with a Waste event for StoreNumber '251' containing one WasteDetail line with ItemCode 'PBMSANDWICH01', Quantity 4, UOM 'Each', WasteType 'FinishedWaste', WasteReason 'End of day', and ProductionBOMWasteMethod 'MakeAndWaste'

Key Endpoints

2 endpoints — the mx.

METHOD

PATH

DESCRIPTION

POST

/External/Inventory/Webhook/

Post a production BOM, transfer, or waste event

POST

/External/QuBeyond/WebhookAnonymous

Post a QuBeyond back-of-house inventory event

POST

/External/Inventory/Webhook/

Post a production BOM, transfer, or waste event

POST

/External/QuBeyond/WebhookAnonymous

Post a QuBeyond back-of-house inventory event

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring these Macromatix webhooks by hand means managing basic-auth credentials, building the event envelope with type, id, source, and timestamp around each payload, and parsing InvalidRecordIndex to find failed lines. Through Jentic you install once, import the API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Both webhooks carry the store number inside the request body, so rules bound which operations your agent may call, not which store it posts for. You choose the operations it may call, so the QuBeyond webhook is not included unless you add it.

Credential isolation

Your Macromatix basic-auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'log waste in Macromatix' or 'send a stock transfer between stores', and Jentic returns the matching webhook operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Mx.Web.WebAPIs API through Jentic.

Is there a Macromatix MCP server?

You don't need an MCP server to give your agent these Macromatix webhooks. Jentic connects them directly from the API Directory: import the API, store your basic-auth credentials once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

What authentication does the Mx.Web.WebAPIs API use?

Per its OpenAPI spec, both webhooks use HTTP basic authentication with a username and password in the Authorization header, and invalid credentials return 401. Through Jentic, the credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never enter the agent's context.

Can I limit what my agent is allowed to do with the Mx.Web.WebAPIs API?

Yes. Write a rule that allows only POST /External/Inventory/Webhook/. Your agent can then post production, transfer, and waste events, but it cannot post to the QuBeyond webhook, and every call it makes is logged.

How do I post a waste event to Macromatix through Jentic?

Search Jentic for 'log waste in Macromatix', load the External Inventory webhook operation, and call POST /External/Inventory/Webhook/ with an event whose Data holds a StoreNumber and WasteDetail lines. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Why did Macromatix reject part of my event?

The webhook returns 400 for incorrect input such as a store number that is not found. The response's Messages array explains what failed, for example an item code with no matching BOM make item, and InvalidRecordIndex lists the positions of the rejected records so you can fix and resend only those.

Mxdev Mobile Mx.Web.WebAPIs

AI ReadinessNon-Ready (F)0/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceInventorybasic2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Post inventory events into a Macromatix back-of-house instance: production BOM makes, store-to-store transfers, and waste through the External Inventory webhook, and counts, purchase orders, and credit memos through the QuBeyond webhook.

Use for: I need to record this morning's sandwich production batch in Macromatix, Send a midday replenishment transfer from the hub to store 15, Log the end-of-day finished waste for store 251, Check whether any lines in my waste event were rejected

Not supported: Does not read inventory levels, list items, or manage suppliers, and it exposes no query endpoints. Use for posting inventory events into a Macromatix back-of-house instance only.

The Mx.Web.WebAPIs API accepts inventory event payloads into a Macromatix back-of-house instance, here the production host labelled Pret's Production. Its External Inventory webhook takes events for production bill-of-materials makes, stock transfers between stores, and waste, each keyed by store number and item code with quantities, units, and timestamps. A second QuBeyond webhook takes back-of-house events such as inventory counts, purchase orders, transfers, waste, credit memos, and BOM makes. Both endpoints use HTTP basic authentication and return a status, a message type, and the index of any record that failed validation, such as an unknown store number or item code.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

36%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

15%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

10%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Mx.Web.WebAPIs to your agent

Capabilities

Start building with Mx.Web.WebAPIs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mxdev Mobile Mx.Web.WebAPIs

Jentic AI Readiness Score

Mx.Web.WebAPIs

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness