Community operators
Launch embedded storefronts, configurator handoffs, and community flows inside club, league, and company sites with versioned public contracts.
Developer platform
Developer APIs, embeds, and AI tools for custom merchandise
Use MerchandAise APIs, OpenAPI contracts, community embeds, supplier workflows, enterprise identity, and MCP tools to connect custom merchandise into websites, portals, and AI agents.
Who builds with MerchandAise
Enterprise teams and platform partners
Connect procurement portals, identity systems, and internal operations to merchandise workflows without rebuilding approval and supplier logic.
AI agent and automation builders
Give assistants structured tool access for discovery, quoting, and approved operations through MCP-compatible endpoints.
Developer platform
Integration surfaces and contracts
01
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.
02
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.
Community embed API
Connect localized club, community, or storefront experiences to MerchandAise-owned design and commerce handoffs without rebuilding the underlying workflow.
Supplier API
Connect approved suppliers to onboarding, catalog, quote, and fulfillment operations after the supplier relationship and access model are qualified.
Enterprise identity API
Plan SSO, SCIM provisioning, and audit-ready identity flows for approved company merchandise programs and governed rollouts.
Review enterprise integration guide
Enterprise identity OpenAPI JSON
01 — 03
Integration quickstart
01
Choose the contract that matches your workflow
Start with the surface that matches your user and auth model: community embed, enterprise identity, supplier operations, or MCP tools for assistants.
02
Validate auth, versioning, and environment boundaries
Confirm required headers, scopes, callback expectations, and contract versions in staging before you route production traffic.
03
Test end-to-end workflows before launch
Verify requests, webhooks, provisioning, observability, and rollback paths so the integration is reliable from first live usage.
What production-ready means
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.
01
Sandbox and access review
Confirm which contracts are public, which enterprise surfaces require approval, and which credentials or workspace roles are needed before launch.
02
Versioned implementation evidence
Keep generated clients, callback URLs, auth scopes, contract versions, and rollback ownership documented before production traffic is enabled.
03
Operational observability
Plan logs, retries, support ownership, failure states, and health checks for every workflow that can affect an order, supplier, or enterprise user.
Need an integration review?
Share your architecture, rollout timeline, and destination channels. We will recommend the right contract surface, auth pattern, and launch sequence.