Skip to main content
OmniCommerce’s public MCP endpoint lets agent hosts search and compare merchant products without an OmniCommerce account, seller login, subscription, API key or OAuth connection. Connector availability inside Muse depends on Meta’s review.

​
Connection

Rate-limited requests return HTTP 429 with Retry-After. Use bounded backoff.

​
Public shopping research

  • Search products by merchant, brand, category, stock, explicit currency and price range, rating, variant options or date added.
  • Compare up to ten product IDs using normalized public prices, recorded inventory, structured variant attributes, ACO readiness and marketplace coverage. Results preserve requested order and identify missing products individually.
  • Read complete product details, with stored capabilities, FAQs, citations and localizations attached to the product. Compatible hosts can display portable MCP Apps product cards; other hosts receive structured JSON and text.
Examples:
  • “Find laptops under SGD 1500 in the public merchant catalog.”
  • “Compare these products by price, recorded stock and marketplace coverage.”
  • “Find a lightweight travel laptop and show the matching product details.”
Search, product details and comparison support Shopee, Lazada, TikTok, Shopify, WhatsApp, Zalora, Amazon and eBay. Stored enrichment is optional product data, rather than a separate discovery capability. Products without enrichment remain available. Prices and inventory are recorded catalog data, not a live reservation or delivery guarantee. Currency accompanies monetary values. A lowest-price comparison is only made when the selected priced products use the same currency; currencies are never combined into an unlabeled ranking. The connector exposes public product information. It does not grant access to private seller costs, orders, account records or credentials.

​
Tools

productIds is required, trimmed, deduplicated in requested order and bounded to ten submitted entries. An optional merchantIds array scopes comparison to up to twenty merchants. A missing or inaccessible product produces a per-product error and success: false; successful targets remain available in a partial result. A one-product array is valid. Singular productId arguments are rejected.

​
Public API parity

The same canonical catalog services power MCP and the public REST API:
  • GET /api/v1/catalog/products?productIds=first-product-id,second-product-id returns ordered per-product results with the full public-page projection. Product-level ACO/GEO data is included where stored; no AI generation or embeddings are performed.
  • GET /api/v1/search returns price, currency, inventoryQuantity, inStock, itemGroupId, isVariant, variationAttributes, variantOptions and marketplaceOffers where available.
  • GET /api/v1/compare?products=first-product-id,second-product-id returns the same public comparison facts, structured variants and currency-safe recommendations. REST comparison accepts two to ten product IDs; the MCP batch also accepts one.
An inventory quantity of zero means recorded out of stock. A null quantity or availability means unknown. Marketplace coverage describes recorded listings and does not prove that every marketplace has current stock.

​
Checkout scope

Checkout, payment, delivery booking, shipment tracking, returns and refunds are excluded from this public connector. Product links are reference links, not purchase confirmations. Public product discovery does not enable a merchant to accept direct orders. Configured merchants have a separate buyer-agent purchase interface. That interface is not part of this Muse submission. Adding purchases requires a participating merchant and verified commercial, payment and fulfillment capabilities first. See the MCP guide for transport and resource details.