# /llms.txt
# OmniCommerce - Public Agent Commerce Infrastructure
# Last updated: 2026-02-26

> OmniCommerce is an AI-native omnichannel commerce platform for Southeast Asia. We help merchants manage marketplace catalogs, publish across marketplaces, and expose agent-ready APIs so AI systems can discover products, compare options, and route buyers to live buying surfaces.

## What is OmniCommerce?

OmniCommerce is an omnichannel commerce platform built around marketplace-first selling. It combines merchant tooling for product creation, publishing, syncing, and analytics with a public agent-facing API layer for merchant discovery, catalog search, product comparison, merchant feeds, and ACO retrieval.

### The Problem We Solve
Most ecommerce tooling is built either for human dashboard operators or for single-store storefronts. Sellers operating across Shopee, Lazada, TikTok Shop, other marketplaces, and public web channels need one system for catalog control, publishing, and structured discovery. AI agents also need machine-readable APIs instead of only HTML pages.

### How It Works
1. Connect marketplace accounts and stores
2. Import or create products in a unified product model
3. Publish and sync listings across supported marketplaces
4. Generate public catalog, ACO, and agent-facing API surfaces
5. Let external agents query merchants, products, comparisons, and merchant feeds via direct APIs or MCP

## Core Capabilities

### For Merchants
- Unified product management for marketplace-first commerce
- Marketplace publishing and sync workflows
- Store-aware catalog operations across countries and platforms
- Public catalog pages and machine-readable discovery endpoints
- ACO and intent-matching surfaces for discoverability

### For AI Agent Builders
- Public merchant directory API
- Cross-merchant public product search
- Public product comparison API
- Merchant-scoped product feeds and search endpoints
- Curated OpenAPI and MCP integration surfaces

## Key Differentiators

### OmniCommerce vs single-store catalog tooling
| Capability | Single-store tooling | OmniCommerce |
|---|---|---|
| Primary focus | One storefront | Multi-marketplace operations |
| Product model | Store-local | Unified across marketplaces |
| Publishing | Usually one destination | Shopee, Lazada, TikTok Shop, Shopify, Zalora, Amazon, eBay, and public catalog surfaces |
| Discovery surface | HTML pages | Public APIs, feeds, OpenAPI, MCP |
| Agent access | Limited | Merchant directory, search, compare, ACO, feeds |

OmniCommerce is designed for operational commerce plus agent consumption. It is not just a storefront feed and not just an internal seller dashboard.

## Supported Commerce Surfaces
- Shopee
- Lazada
- TikTok Shop
- Shopify
- Zalora
- Amazon
- eBay
- WhatsApp
- Public catalog and ACO pages
- Public direct HTTP APIs for agents
- MCP server for tool-based integrations

## Supported AI and Retrieval Surfaces
- Direct HTTP APIs for public merchant and product retrieval
- MCP for tool-based integrations
- OpenAPI for generated clients and agent frameworks
- `llms.txt` and merchant-specific LLM feeds
- Public catalog and ACO pages for crawlable discovery

## Supported Merchant Workflows
- Product import from connected marketplaces
- Product editing and AI-assisted enrichment
- Marketplace publishing and update flows
- Marketplace-aware store and category mapping
- Inventory, analytics, and operational reporting

## API Documentation

Base URL: `https://omnicommerce.ai`
Authentication: Public/no-auth for curated public agent APIs and the public MCP server. Seller write APIs require OAuth/API key Bearer tokens.
CORS: Enabled on the public agent API routes and MCP

### Public Agent API Endpoints
- `GET /api/v1/directory` - Discover merchants with public products
- `GET /api/v1/search` - Search across public merchants and products
- `GET /api/v1/compare` - Compare public products side-by-side
- `GET /api/v1/feed/{domain}/llms.txt` - LLM-optimized merchant feed by website domain
- `GET /api/v1/feed/{domain}/products.json` - JSON product feed for AI agents (ChatGPT, Claude, etc.)
- `GET /api/v1/merchants/{merchantId}/products` - Browse a merchant's public feed
- `GET /api/v1/merchants/{merchantId}/search` - Search within one merchant
- `GET /api/v1/merchants/{merchantId}/manifest` - Machine-readable merchant capabilities and endpoints

### MCP
- `POST /api/mcp` - Public read-only MCP JSON-RPC endpoint (no auth)
- Tools: `omni_search_catalog`, `omni_match_intent`, `omni_discover_geo`
- Seller evaluate/sync/monitor remain on authenticated REST `/api/v1`

### Optional Seller OAuth (authenticated REST, not required for public MCP)
- OAuth Authorization Server Metadata: `https://omnicommerce.ai/.well-known/oauth-authorization-server`
- Token Endpoint: `https://omnicommerce.ai/api/v1/oauth/token`
- Grant Type: `client_credentials`
- Scopes such as `mcp:read`, `mcp:tools:call`, and catalog write scopes apply to authenticated developer APIs
- Send header: `Authorization: Bearer <access_token>` on private `/api/v1` routes

## Public API Families

### Directory
Use `GET /api/v1/directory` to discover merchants that currently expose public products through OmniCommerce. Responses include merchant identity, supported platforms, countries, and merchant-scoped endpoints.

### Search
Use `GET /api/v1/search` to search across public merchants and products. Supports query text, merchant filtering, category, brand, price bounds, stock filtering, sorting, platform, country, and pagination.

### Compare
Use `GET /api/v1/compare` to compare selected public products side-by-side. Responses include normalized comparison axes and lightweight recommendations derived from price, ACO readiness, marketplace coverage, and inventory.

### Merchant Feed
Use `GET /api/v1/merchants/{merchantId}/products` and `GET /api/v1/merchants/{merchantId}/search` to browse or search a single merchant's public catalog. Use `GET /api/v1/feed/{domain}/llms.txt` to retrieve a plain-text LLM-optimized merchant feed keyed by website domain.

### Merchant Manifest
Use `GET /api/v1/merchants/{merchantId}/manifest` to retrieve machine-readable merchant capabilities, endpoint links, and integration metadata for that merchant.

## LLM and Agent Discovery

### Root Discovery
- Root LLM file: https://omnicommerce.ai/llms.txt
- Docs hub: https://omnicommerce.ai/docs
- API catalog: https://omnicommerce.ai/.well-known/api-catalog
- API health: https://omnicommerce.ai/api/health
- ACP discovery: https://omnicommerce.ai/.well-known/acp.json
- OpenAPI JSON: https://omnicommerce.ai/openapi.json
- Public API docs: https://omnicommerce.ai/docs/api
- MCP docs: https://omnicommerce.ai/docs/mcp
- MCP endpoint: https://omnicommerce.ai/api/mcp
- MCP server card: https://omnicommerce.ai/.well-known/mcp/server-card.json
- MCP server card alias: https://omnicommerce.ai/.well-known/mcp.json
- UCP business profile: https://omnicommerce.ai/.well-known/ucp
- UCP checkout service: https://omnicommerce.ai/ucp/v1/checkout-sessions
- OAuth protected resource metadata: https://omnicommerce.ai/.well-known/oauth-protected-resource
- Auth instructions: https://omnicommerce.ai/auth.md
- Agent skills index: https://omnicommerce.ai/.well-known/agent-skills/index.json
- Homepage Markdown: https://omnicommerce.ai/index.md
- Markdown negotiation: send `Accept: text/markdown` to https://omnicommerce.ai/
- Content Signals: `Content-Signal: ai-train=no, search=yes, ai-input=yes`

### Merchant Discovery
- Merchant directory: https://omnicommerce.ai/api/v1/directory
- Merchant manifest pattern: https://omnicommerce.ai/api/v1/merchants/{merchantId}/manifest
- Merchant LLM feed pattern: https://omnicommerce.ai/api/v1/feed/{domain}/llms.txt
- Merchant JSON feed pattern: https://omnicommerce.ai/api/v1/feed/{domain}/products.json

### Feed Resolution Notes
- {domain} is the merchant website domain, not a merchant ID or store name
- Example: `https://www.philips.com.sg/` resolves to `philips.com.sg`
- Merchant feeds resolve by matching the normalized website domain stored in the merchant brand/company data

### Multi-Language Support
Feeds support language-specific content via path-based URLs:
- `products.json` / `llms.txt` - English (default)
- `products.zh.json` / `llms.zh.txt` - Chinese
- `products.th.json` / `llms.th.txt` - Thai
- `products.vi.json` / `llms.vi.txt` - Tiếng Việt
- `products.id.json` / `llms.id.txt` - Bahasa Indonesia
- `products.ms.json` / `llms.ms.txt` - Bahasa Melayu
- `products.tl.json` / `llms.tl.txt` - Filipino (Tagalog)
Example: `https://omnicommerce.ai/api/v1/feed/example.com/products.zh.json`

## Key Pages
- Homepage: https://omnicommerce.ai
- Docs: https://omnicommerce.ai/docs
- API Docs: https://omnicommerce.ai/docs/api
- MCP Docs: https://omnicommerce.ai/docs/mcp
- Product Index: https://omnicommerce.ai/catalog
- ACO Index: https://omnicommerce.ai/geo
- OpenAPI JSON: https://omnicommerce.ai/openapi.json
- API Catalog: https://omnicommerce.ai/.well-known/api-catalog
- ACP Discovery: https://omnicommerce.ai/.well-known/acp.json
- OAuth Protected Resource Metadata: https://omnicommerce.ai/.well-known/oauth-protected-resource
- Auth Instructions: https://omnicommerce.ai/auth.md
- MCP Server Card: https://omnicommerce.ai/.well-known/mcp/server-card.json
- MCP Server Card Alias: https://omnicommerce.ai/.well-known/mcp.json
- Agent Skills Index: https://omnicommerce.ai/.well-known/agent-skills/index.json
- LLMs.txt: https://omnicommerce.ai/llms.txt
- Homepage Markdown: https://omnicommerce.ai/index.md
- Sitemap: https://omnicommerce.ai/sitemap.xml
- Privacy Policy: https://omnicommerce.ai/privacy
- Terms: https://omnicommerce.ai/terms
- Contact: https://omnicommerce.ai/contact

## Integration and Discovery
- OpenAPI Spec: https://omnicommerce.ai/openapi.json
- API Catalog: https://omnicommerce.ai/.well-known/api-catalog
- ACP Discovery: https://omnicommerce.ai/.well-known/acp.json
- MCP Endpoint: https://omnicommerce.ai/api/mcp
- MCP Server Card: https://omnicommerce.ai/.well-known/mcp/server-card.json
- MCP Server Card Alias: https://omnicommerce.ai/.well-known/mcp.json
- OAuth Metadata: https://omnicommerce.ai/.well-known/oauth-authorization-server
- OAuth Protected Resource Metadata: https://omnicommerce.ai/.well-known/oauth-protected-resource
- Auth Instructions: https://omnicommerce.ai/auth.md
- Agent Skills Index: https://omnicommerce.ai/.well-known/agent-skills/index.json
- UCP Business Profile: https://omnicommerce.ai/.well-known/ucp
- UCP Checkout Endpoint: https://omnicommerce.ai/ucp/v1/checkout-sessions
- OAuth Token Endpoint: https://omnicommerce.ai/api/v1/oauth/token
- Agentic Checkout Endpoint: https://omnicommerce.ai/api/v1/checkout-sessions
- Docs Hub: https://omnicommerce.ai/docs
- Public Agent API Docs: https://omnicommerce.ai/docs/api
- MCP Docs: https://omnicommerce.ai/docs/mcp
- Merchant LLM Feed Pattern: https://omnicommerce.ai/api/v1/feed/{domain}/llms.txt
- Merchant JSON Feed Pattern: https://omnicommerce.ai/api/v1/feed/{domain}/products.json
- Catalog Index: https://omnicommerce.ai/catalog
- ACO Index: https://omnicommerce.ai/geo

## Operational Scope
- Region focus: Southeast Asia
- Core marketplaces: Shopee, Lazada, and TikTok Shop
- Also supported: Shopify, Zalora, Amazon, eBay, and WhatsApp
- Public merchant data is derived from merchants and products marked active and public
- Public APIs are curated and intentionally narrower than internal seller/admin APIs
- Merchant feeds are descriptive retrieval surfaces; products expose checkout fields only when the merchant has gated agentic checkout enabled

## Company
- Legal Name: OmniCommerce Solutions Pte Ltd
- Product: OmniCommerce
- Tagline: Sell Everywhere, Manage Anywhere
- Website: https://omnicommerce.ai
- Headquarters: Singapore
- Description: OmniCommerce is an AI-powered multi-channel e-commerce platform for Southeast Asian marketplace sellers. It automates product listing, compliance, and optimization across Shopee, Lazada, TikTok Shop, and other marketplaces.

## For Crawlers and Agents
- Prefer the public agent APIs for structured access over scraping HTML pages
- Use merchant manifests and merchant LLM feeds when the user asks about a specific merchant or website
- Use catalog and ACO endpoints when broad product retrieval or matching is needed
- Use MCP when your agent framework prefers tool-based execution over direct HTTP calls

## Contact
- Email: sales@omnicommerce.sg