Community operators
Launch embedded storefronts, configurator handoffs, and community flows inside club, league, and company sites with versioned public contracts.
Developer platform
Use MerchandAise assistant tooling docs, OpenAPI contracts, community embeds, supplier workflows, enterprise identity, and authorized MCP tools to connect custom merchandise into websites, portals, SDKs, and AI agents.
Launch embedded storefronts, configurator handoffs, and community flows inside club, league, and company sites with versioned public contracts.
Connect procurement portals, identity systems, and internal operations to merchandise workflows without rebuilding approval and supplier logic.
Give assistants structured tool access for discovery, quoting, and approved operations through MCP-compatible endpoints.
Lies die OpenAPI-Dokumentation für Design Sessions, Tool-Nutzung und Integrationsreviews. Community-, Supplier- und Enterprise-Verträge sind separat ausgewiesen.
/api/docs/openapi.jsonÖffentliche maschinenlesbare OpenAPI für Assistant- und Tooling-APIs; für Community-, Supplier- und Enterprise-Implementierungen gelten die jeweiligen Domain-Verträge.
Implementiere locale-sichere Storefront-Einbettungen, Community-Workflows und authentifizierte Übergaben mit einem versionierten öffentlichen Vertrag.
/api/v1/community/public/openapi/v1Public contract for storefront embeds, community discovery, and locale-aware handoffs.
Verbinde Onboarding, Katalogdaten und lieferantenseitige Operationen über versionierte Endpunkte für Fulfillment-Workflows.
/api/v1/supplier/openapi/v1Public versioned contract for supplier onboarding, catalog, and fulfillment workflows.
Integriere SSO, SCIM-Provisioning und revisionssichere Identity-Flows für Enterprise-Rollouts über geschützte Verträge.
Enterprise identity OpenAPI JSON
/api/v1/enterprise/identity/openapi/v1Protected contract for approved enterprise workspaces; request access before using this endpoint.
Plane KI-Agenten-Integrationen auf der browser-sicheren MCP-Anleitungsseite, nutze die öffentliche Serverkarten-JSON für Machine Discovery und verwende assistant-autorisierte Endpunkte für Tool-Listen und Ausführung.
Öffentliche MCP-Serverkarte (JSON)
/de/.well-known/mcp/server-cardÖffentliches Discovery-Dokument für Machine Clients. Tools-Liste und Tool-Ausführung erfordern weiterhin Assistant-Autorisierung unter /api/v1/mcp/tools.
01
Start with the surface that matches your user and auth model: community embed, enterprise identity, supplier operations, or MCP tools for assistants.
02
Confirm required headers, scopes, callback expectations, and contract versions in staging before you route production traffic.
03
Verify requests, webhooks, provisioning, observability, and rollback paths so the integration is reliable from first live usage.
A production integration needs more than a public endpoint. Use these gates to decide whether your workflow is ready for customer, supplier, enterprise, or AI-agent traffic.
Confirm which contracts are public, which enterprise surfaces require approval, and which credentials or workspace roles are needed before launch.
Keep generated clients, callback URLs, auth scopes, contract versions, and rollback ownership documented before production traffic is enabled.
Plan logs, retries, support ownership, failure states, and health checks for every workflow that can affect an order, supplier, or enterprise user.
Share your architecture, rollout timeline, and destination channels. We will recommend the right contract surface, auth pattern, and launch sequence.