Saleor

{
  "service_type": "platform",
  "base_url": "https://saleor.io",
  "auth_method": "token",
  "auth_config": {
    "type": "app_token",
    "header_name": "Authorization",
    "header_format": "Bearer <token>",
    "notes": "GraphQL API on each Saleor instance (typically https://<instance>.saleor.cloud/graphql/) requires a Saleor app token. MCP server requires headers X-Saleor-API-URL and X-Saleor-Auth-Token, with app permissions MANAGE_PRODUCTS and MANAGE_ORDERS.",
    "per_operation_permissions": true
  },
  "endpoints": [
    {
      "name": "Storefront GraphQL API",
      "url_pattern": "https://<instance>.saleor.cloud/graphql/",
      "protocol": "GraphQL",
      "method": "POST",
      "description": "Main commerce GraphQL API for storefront development and integrations. saleor.io itself is not an API endpoint."
    },
    {
      "name": "Saleor MCP server (read-only)",
      "url": "https://mcp.saleor.app/mcp",
      "protocol": "Streamable HTTP (MCP)",
      "method": "POST",
      "description": "Read-only access to connected store commerce data (products, orders). Requires headers X-Saleor-API-URL and X-Saleor-Auth-Token. Hosted compatibility: *.saleor.cloud instances, Saleor 3.21+."
    },
    {
      "name": "Markdown content delivery",
      "url_pattern": "https://saleor.io/<path>.md (e.g. /index.md, /pricing.md, /features/*.md, /solutions/*.md, /blog/*.md)",
      "protocol": "HTTP",
      "method": "GET",
      "description": "Server-rendered pages available as Markdown for agents. HTML pages advertise their Markdown URL via a Link response header."
    },
    {
      "name": "Sitemap",
      "url": "https://saleor.io/sitemap.xml",
      "protocol": "HTTP",
      "method": "GET",
      "description": "Discover published page URLs."
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "open_source": "Saleor is open-source and can be self-hosted (https://github.com/saleor/saleor).",
      "cloud": "Managed Saleor Cloud plans with commercial terms. Pricing must be read from https://saleor.io/pricing.md; Cloud pricing should not be inferred from the open-source license."
    }
  },
  "rate_limits": {
    "known": false,
    "notes": "No rate limits disclosed on the marketing site. Consult API documentation for per-instance limits."
  },
  "capabilities": [
    "headless commerce backend (GraphQL-first)",
    "custom storefront development",
    "multi-channel and multi-market commerce",
    "integration with existing business systems",
    "open-source self-hosting",
    "managed cloud hosting (Saleor Cloud)",
    "app ecosystem / App Store integrations",
    "read-only MCP agent access to products and orders",
    "declarative store configuration via Saleor Configurator CLI (YAML, Commerce as Code)",
    "agentic commerce",
    "GraphQL API with typed queries, mutations, inputs, and responses",
    "markdown rendering of website content for agent consumption"
  ],
  "raw_analysis": "Saleor is an open-source, GraphQL-first headless commerce platform aimed at development teams building custom commerce experiences. It is not a consumer SaaS dashboard but a commerce backend: teams build and connect their own storefronts and customer experiences, while Saleor provides the commerce engine. It is best suited for organizations needing custom storefronts, multi-channel/multi-market commerce, or integration with existing business systems. Teams wanting a ready-made storefront without engineering effort should look elsewhere.\n\nMaturity and integrations: Saleor is a mature open-source project (GitHub: saleor/saleor) with a managed cloud offering and an App Store ecosystem. A documented case study (Lush) demonstrates multi-market customer implementation. The platform emphasizes composable architecture and extensibility, and has published an agentic commerce approach.\n\nAPI access: The primary API is a per-instance GraphQL endpoint, typically https://<instance>.saleor.cloud/graphql/. Note that saleor.io is the marketing website, not a shared commerce API. Authentication uses Saleor app tokens with per-operation permissions. Documentation is at docs.saleor.io, with an API reference, GraphQL overview, and app quickstart.\n\nAgent/MCP integration: Saleor publishes an MCP server (https://mcp.saleor.app/mcp) that is explicitly read-only, exposing commerce data such as products and orders. It is not capable of checkout or other mutations. It requires headers X-Saleor-API-URL and X-Saleor-Auth-Token, an app token with MANAGE_PRODUCTS and MANAGE_ORDERS permissions, and works with Saleor Cloud instances under *.saleor.cloud on Saleor 3.21+. Self-hosted users must run their own MCP server. Source and setup instructions are at github.com/saleor/saleor-mcp.\n\nTooling: Saleor Configurator (npx @saleor/configurator) provides declarative YAML-based store configuration with read and deploy (mutating) operations, referred to as Commerce as Code. Release compatibility with the target Saleor ver

3/3 tests passed

{
  "overall": 82,
  "dimensions": {
    "token_efficiency": 9.0,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 7.5,
    "doc_quality": 8.5,
    "auth_simplicity": 7.5,
    "latency": 9.5,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "freemium",
    "open_source": "free (self-hosted, Apache-2.0 style community edition)",
    "cloud": "managed plans, pricing at saleor.io/pricing.md",
    "note": "Do not infer Cloud cost from OSS license"
  },
  "issues": [
    "Cloud pricing not directly visible in the evidence — requires a separate fetch of saleor.io/pricing.md",
    "Self-hosting requires significant DevOps effort, so 'first try success' depends on mode (Cloud vs OSS)",
    "MCP agent access is described as read-only (products, orders) — limited write/action surface for agents"
  ],
  "recommendations": [
    "Surface headless/GraphQL + llms.txt compliance as the primary agent-onboarding pitch — it's rare and valuable",
    "Recommend Saleor Cloud for users wanting fast time-to-value; recommend OSS only for teams with infra capacity",
    "Use the Configurator CLI / Commerce-as-Code YAML story for reproducibility in agent workflows"
  ]
}