commercelayer.io
Commerce Layer exposes three HTTP APIs (Core at `https://yourdomain.commercelayer.io`, Metrics at `https://{{your_domain}}.commercelayer.io/metrics`, and Provisioning at `https://provisioning.commercelayer.io`), three MCP servers (Core, Metrics, and a public Docs MCP), and a CLI; Core/Metrics use Commerce Layer OAuth bearer tokens from Core API credentials, Provisioning uses its own client-credentials bearer token, Docs MCP is unauthenticated, and CLI auth is undocumented.
- Commerce Layer Documentation MCPdiscovered
- Commerce Layer Core MCPdiscovered
- Commerce Layer Metrics MCPdiscovered
- Commerce Layer Core APIdiscovered
- Commerce Layer Metrics APIdiscovered
- Commerce Layer Provisioning APIdiscovered
- Commerce Layer CLIdiscovered
Sign in to the Commerce Layer Dashboard. Under Settings > API credentials, create the appropriate Core API client: sales channel, integration, or webapp, as described in the API credentials docs. Use its client_id and, for confidential clients (integration or webapp), client_secret to obtain bearer tokens from https://auth.commercelayer.io/oauth/token per the authentication guide.
Sign in to the Commerce Layer Dashboard, open your profile menu, and select Provisioning API. Copy the issued client_id and client_secret, then exchange them for a bearer token at https://auth.commercelayer.io/oauth/token with grant_type=client_credentials as shown in the Provisioning authorization docs.
conventions · 1/7 published
- integrations.json——
- llms.txt✓https://commercelayer.io/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing