Thyris Merchant Services Documentation
This documentation supports merchants integrating with Thyris Merchant Services.
Use these documents during onboarding, technical integration, QA, and production handoff.
What Thyris Merchant Services Is
Thyris Merchant Services is the merchant readiness layer of the Thyris Agentic Commerce platform. It prepares merchants for agentic commerce and procurement by turning merchant systems into controlled, observable, agent-accessible capabilities.
The platform gives merchants and integration teams the surfaces needed to connect product catalogs, carts, orders, supplier workflows, procurement inventory, quotes, purchase orders, webhooks, MCP tools, UCP-compatible APIs, API keys, store scopes, team access, diagnostics, and operational dashboards. The main work is merchant readiness: making catalog, checkout, procurement, and integration data safe and usable by agentic commerce flows.
Thyris Agentic Commerce handles the agent experience and controlled tool access. Thyris Merchant Services provides the merchant-side operating layer those experiences need: store setup, product and procurement data, tool access, webhooks, order and quote workflows, payment preparation, and production support controls.
Feature Areas
| Area | What It Enables |
|---|---|
| Merchant and store management | Multi-merchant, sub-merchant, store, team, role, settings, and scoped API keys with configurable expiration, revocation, and revoke-before-delete lifecycle. |
| Catalog readiness | Product, variant, optional multi-image galleries, price, inventory, bulk product actions, cart, checkout, and order data for agent-facing commerce. |
| AI merchandising | Product enrichment, provider management, usage reporting, tags, and hyperpersonalization campaigns. |
| Procurement readiness | Suppliers, procurement inventory with optional galleries, bulk table actions, reorder policies, quote requests, supplier email replies, approvals, purchase orders, and order lifecycle tracking. |
| Agentic commerce access | Remote MCP tools and UCP-compatible APIs for controlled catalog and procurement operations. |
| Agent operations | Agent instances, ARP gateways and policies, Routers, ACP settings, and visual commerce flows. |
| Payments and channels | Payment provider instances, crypto wallets, hosted chatbots, and WhatsApp connections. |
| Marketplace | Store-scoped installation of agents, MCP servers, payment providers, and extensions. |
| Integration surfaces | REST APIs, inbound webhooks, outbound webhooks including MCP-triggered events, UCP, MCP, and sample scripts. |
| Operations and security | API scopes, webhook secrets, audit/activity logging, diagnostics, two-factor authentication, and operational dashboards. |
| Extension and adapter patterns | Commerce adapters can map source platforms into Thyris catalog, cart, checkout, and procurement contracts without exposing platform-specific names in customer documentation. |
Recommended Reading Order
| Step | Document | Purpose |
|---|---|---|
| 1 | Overview | What Thyris Merchant Services is, what it is not, and how it supports Thyris Agentic Commerce. |
| 2 | Merchant Readiness Checklist | Business, operational, catalog, checkout, and procurement readiness questions before technical work starts. |
| 3 | Integration Selection Guide | Choose REST, webhook, UCP, MCP, scripts, or a combined integration model. |
| 4 | Dashboard Setup | Set up merchant account, stores, sub-merchants, API keys, and access scopes. |
| 5 | Store Dashboard Services | Understand the operational services available inside each store. |
| 6 | Solution Scenarios | Select a readiness, procurement, WhatsApp AI chat, merchandising, agent operations, or integration operating model. |
| 7 | Getting Started | First technical rollout steps after the integration path is selected. |
| 8 | Authentication and Scopes | API key usage, headers, scope model, and key handling. |
| 9 | Enterprise API Documentation | Complete public API map, authentication, conventions, examples, errors, and optional Postman companion. |
| 10 | Catalog Data Model | Catalog, cart, order, and common object model. |
| 11 | Catalog REST API and Catalog Webhooks | Catalog API and webhook implementation details. |
| 12 | Procurement REST API and Procurement Webhooks | Procurement API and webhook implementation details. |
| 13 | Merchant MCP, UCP Catalog, and UCP Procurement | Agent/protocol access surfaces when needed. |
| 14 | Request Field Requirements and Sample Scripts | Field reference and executable samples for implementation teams. |
| 15 | Testing and Troubleshooting | QA, troubleshooting, and production launch checks. |
The sequence intentionally starts with product scope and readiness, then moves toward technical implementation.
Document Index
| Document | Purpose |
|---|---|
| Overview | Product overview of Thyris Merchant Services as the merchant readiness platform for Thyris Agentic Commerce. |
| Merchant Readiness Checklist | What the merchant's own systems should support before POC or production. |
| Integration Selection Guide | How to choose REST, webhook, UCP, MCP, or script-based integration. |
| Dashboard Setup | Merchant account, store creation, sub-merchants, API keys, and key types. |
| Store Dashboard Services | Service map for Catalog, Enrichment, Hyperpersonalization, Readiness, Procurement, Agents, ARP, Router, Agentic Commerce, Payments, Chatbots, and Marketplace. |
| Solution Scenarios | Detailed platform scenarios for readiness, procurement, enterprise WhatsApp AI chat, merchandising, agent operations, and integrations. |
| Store Dashboard Use Cases | Cross-service scenarios for launch, automation, integrations, payments, campaigns, and incident response. |
| Getting Started | Integration overview, prerequisites, and recommended rollout order. |
| Authentication and Scopes | API key creation, headers, access scopes, and key handling. |
| Enterprise API Documentation | Unified reference for REST, webhooks, UCP, MCP, errors, and integration examples. |
| Catalog Data Model | Product, variant, cart, order, and common JSON field reference. |
| Catalog REST API | REST catalog endpoints for stores, products, carts, and orders. |
| Catalog Webhooks | Inbound catalog sync and outbound catalog event destinations. |
| Procurement REST API | REST procurement endpoints for suppliers, inventory inputs, quotes, and purchase orders. |
| Procurement Webhooks | Inbound procurement sync and outbound supplier/inventory/order event destinations. |
| Merchant MCP | Remote MCP server setup and available catalog/procurement tools. |
| UCP Catalog | UCP-compatible catalog endpoints and usage notes. |
| UCP Procurement | UCP-compatible procurement endpoints and usage notes. |
| Request Field Requirements | Required and optional fields for every request. |
| Testing and Troubleshooting | Integration checklist, test cases, and common errors. |
| Merchant Webhook Implementation Guide | Catalog-only merchant webhook implementation guide for inbound product sync and outbound catalog receivers. |
| Sample Scripts | Node.js sample scripts and 30-product sample payload. |
Sample Scripts
Use Sample Scripts for terminal-based examples and view the 30-product demo catalog payload directly in the documentation.
Production Endpoints
Dashboard: https://merchant.thyris.cloud/app/merchant-services
REST API: https://merchant.thyris.cloud/api/v1/catalog
Procurement REST API: https://merchant.thyris.cloud/api/v1/procurement
UCP API: https://merchant.thyris.cloud/api/protocols/ucp/catalog
Procurement UCP API: https://merchant.thyris.cloud/api/protocols/ucp/procurement
Webhook ingress: https://webhook.thyris.ai/webhooks/catalog
Procurement webhook ingress: https://webhook.thyris.ai/webhooks/procurement
MCP: https://merchant.thyris.cloud/mcp
Replace the production host with your staging host when testing in a staging environment. Some deployments use customer-specific custom domains; in that case, use the exact dashboard, API, webhook, and MCP domains shared by Thyris or your integration owner instead of the default Thyris hosts.
Required Values
Before implementation starts, the merchant should have:
- A merchant account.
- At least one store.
- A developer API key.
- The target
storeIdfor each store being integrated. - Product source identifiers such as SKU or external product IDs.
- Procurement supplier and inventory identifiers when procurement is integrated.
- Optional webhook destination URL for outbound events.