MerchandAise agent platform

Let agents help. Keep people in control.

Connect an AI assistant to the same design-to-order workflow your buyers use—then grant only the tools it needs and keep every consequential action behind the right confirmation.

One assistant. One governed workflow.

An assistant can help turn a description or uploaded reference into a supported product direction, product-native 3D view, and supplier-backed price, MOQ, and delivery expectations. It should extend the MerchandAise workflow, not create a second source of truth.

The server card and external tool metadata are public for discovery. Each tool call still follows its declared security and workspace boundary, while buyer, proof, and production approvals stay visible and attributable.

01 — Contracts

Discover the server. Then request the right access.

MCP discovery and governed tools

Use the public server card and external tools list for machine discovery, then honor each tool’s declared security, workspace, and confirmation boundaries when an agent executes it.

Access: public

Implementation guide

Read MCP implementation guide

Machine contract

Public MCP server-card JSON

/en-us/.well-known/mcp/server-card

Public discovery document for machine clients. The external tools list at /api/v1/mcp/tools exposes current tool metadata; each tool call still follows its declared security, workspace, and confirmation boundaries.

Assistant tooling API docs

Explore current assistant and tooling endpoints for design sessions and integration review. This public reference does not grant anonymous authority to quote or place an order.

Access: public

Implementation guide

Open assistant tooling docs

Machine contract

Assistant tooling OpenAPI JSON

/api/docs/openapi.json

Public reference for assistant and tooling APIs. Production access and order-affecting operations still require the applicable authorization.

02 — Implementation guide

From discovery to a governed action

01
Discover safely
Use the public MCP server card and tools list to identify MerchandAise and the current external tool inventory. Discovery alone grants no broad authority to quote, change state, or order.
02
Grant the least privilege
Authorize only the tools, workspace, and environment the assistant needs. Separate read-only exploration from actions that change a design, quote, approval, or order state.
03
Confirm before consequence
Keep explicit human confirmation for sensitive actions, test stale-state and refusal behavior, and prove recovery paths before production traffic is enabled.

What the agent must preserve

One versioned product state

The assistant works against the same design, commerce intent, supplier-backed quote, approval, and order state as every other MerchandAise surface.

Commercial and supplier privacy

Where MerchandAise processes the buyer transaction, Hutter Products GmbH is the contracting seller and Merchant of Record under the MerchandAise brand. Private supplier identity, contacts, and internal data are not exposed to an agent.

Proof gates stay human

AI and product-native 3D support the decision, but digital-proof approval and approval of a genuine production sample remain required before mass production.

Before an agent reaches production

A discoverable MCP server is only the beginning. Production readiness means the assistant has a bounded role, every consequential action has an owner, and failures return users to a safe state.

Map access by consequence

Classify every tool as read-only, advisory, state-changing, supplier-sensitive, or order-affecting before granting it to an assistant.

Name every confirmation owner

Define who confirms product changes, quotes, digital proofs, production samples, and orders—and what the assistant does when that person is unavailable.

Observe, refuse, and recover

Test invalid inputs, stale state, missing permissions, refusals, retries, telemetry, and rollback paths before live traffic reaches the workflow.

FAQ

What can an AI agent do with MerchandAise?

An authorized assistant can use the tools approved for its workspace and environment, such as product discovery, design or quote guidance, and other explicitly enabled operations. The available tools and their permissions are determined during integration review.

Can an AI agent place orders automatically?

Not by discovering the server or listing tools. Any order-affecting workflow must preserve authentication, buyer and workspace confirmation, version-current pricing, digital-proof approval, and the genuine-sample gate required before mass production.

Is the MerchandAise MCP integration public?

The MCP server card and current external tool metadata are public for machine discovery. Individual tool calls follow their declared security model, and protected workspace, supplier, enterprise, quote, and order operations retain their required authorization and confirmations.

Have an agent workflow in mind?

Tell us who the assistant serves, what it should be allowed to do, and where a person needs to stay in control. We will map the right MCP, API, and approval boundary.

Review an agent workflow Explore API contracts

One assistant. One governed workflow.

From discovery to a governed action

Discover safely

Use the public MCP server card and tools list to identify MerchandAise and the current external tool inventory. Discovery alone grants no broad authority to quote, change state, or order.

Grant the least privilege

Authorize only the tools, workspace, and environment the assistant needs. Separate read-only exploration from actions that change a design, quote, approval, or order state.

Confirm before consequence

Keep explicit human confirmation for sensitive actions, test stale-state and refusal behavior, and prove recovery paths before production traffic is enabled.