Medusa

{
  "service_type": "platform",
  "base_url": "https://medusajs.com",
  "auth_method": "api_key",
  "auth_config": {
    "notes": "Medusa is self-hosted/open-source; the core platform does not ship with a single first-party REST API surface on medusajs.com. Authentication to a running Medusa instance typically uses API keys (publishable keys for Store API, secret/admin keys for Admin API) or JWT bearer tokens issued by the Auth Module. Medusa Cloud (PaaS) additionally requires account authentication via the Medusa Cloud dashboard.",
    "auth_methods_supported_by_platform": [
      "api_key",
      "bearer_token",
      "oauth2_via_auth_module_identity_providers"
    ]
  },
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "open_source_core": "Medusa is open source and self-hostable at no license cost; you pay only for your own infrastructure.",
      "cloud_paas": "Medusa Cloud is a paid PaaS offering for fully-managed Medusa hosting. Public pricing page: https://medusajs.com/pricing/",
      "search_addon": "Medusa Search is pre-integrated and available on all Medusa Cloud plans, claimed at 50-80% lower cost than Algolia/MeiliSearch.",
      "no_volume_based_fees": "Marketing materials state distributors/B2B users avoid volume-based fees.",
      "notes": "Exact Cloud tiers/prices are not specified in the provided content; consult the pricing page."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Open source headless/digital commerce platform (Medusa v2)",
    "Built-in Framework for deep customization and extensibility",
    "Headless REST/Store API and Admin API for a running instance",
    "Medusa Admin dashboard for store operations",
    "Composable Commerce Modules: API Key, Auth, Cart, Currency, Customer, Fulfillment, Inventory, Order, Payment, Pricing, Product, Promotion, Region, Sales Channel, Stock Location, Tax",
    "Medusa Cloud managed PaaS hosting",
    "Medusa Search (full-text and semantic search) on Cloud plans",
    "Cloud AI Assistant for Medusa Cloud",
    "Log drains for streaming backend/storefront logs to observability platforms",
    "Commerce MCP (beta) and agentic automation tooling",
    "Frontend starters (e.g., Next.js) and community integrations directory",
    "Multi-region, multi-currency, multi-warehouse, multi-sales-channel support",
    "B2B, DTC, marketplace, and distributor commerce solutions",
    "Third-party integrations across payments, fulfillment, search, analytics, auth, ERP, storage",
    "Migration tooling from Shopify and WooCommerce"
  ],
  "raw_analysis": "Medusa (https://medusajs.com) is an open-source, headless digital commerce platform positioned as a highly customizable alternative to hosted platforms like Shopify. Rather than exposing its own public SaaS REST API at the medusajs.com domain, Medusa is software you deploy: once a Medusa server is running, it exposes Store API and Admin API surfaces, and the core is organized into modular \"Commerce Modules\" (Cart, Order, Product, Payment, Pricing, Promotion, Inventory, Fulfillment, Customer, Tax, Region, Currency, Sales Channel, Stock Location, Auth, API Key). Because of this architecture, the primary \"API\" is the instance's own HTTP API, not a centralized service endpoint.\n\nMaturity and ecosystem: Medusa v2 is actively maintained (v2.21.0 security release mentioned, mature module set, changelog and release cadence in blog). It has a growing integration directory (dozens of community integrations across payments, fulfillment, search, analytics, auth, ERP, storage), documented pre-integrated Search, a Cloud AI Assistant, log drains, and a commerce MCP beta, indicating active investment in developer and agent tooling. User stories (e.g., Healthletic's 30% checkout lift after migrating off Shopify Plus on $24M GMV) suggest production readiness at scale.\n\nWho it's for: DTC brands, B2B/commerce operations, distributors, and marketplaces needing deep customization, ERP/PIM/WMS integration, and no volume-based fees. Also suited for teams willing to self-host and build custom workflows.\n\nPricing: The core is free/open source (self-hosted, you bear infrastructure costs). Medusa Cloud is a tiered PaaS offering (see /pricing/) and includes Medusa Search. Exact rates are not specified in the provided content.\n\nIntegrations: Extensive and bidirectional — the platform integrates with third-party payments, fulfillment, search, analytics, auth, ERP, storage, and also provides starters and expert partners, plus one-prompt migration from Shopify/WooCommerce.\n\nCaveats for API consumers: No single public REST API lives at medusajs.com; endpoints depend on your deployed instance's base URL and version. Auth uses API keys and/or JWT/identity providers via the Auth Module. No public rate limits are documented for the core; Cloud-managed deployments may impose their own limits. Anyone integrating with \"Medusa\" as a service should target a specific self-hosted instanc

3/3 tests passed

{
  "overall": 84,
  "dimensions": {
    "token_efficiency": 9.0,
    "first_try_success": 8.0,
    "response_parseability": 9.5,
    "error_clarity": 8.0,
    "doc_quality": 9.5,
    "auth_simplicity": 7.5,
    "latency": 10.0,
    "consistency": 8.5
  },
  "pricing_normalized": {
    "model": "freemium",
    "open_source_core": "free (self-hosted, infra costs only)",
    "cloud_paas": "paid, tiered (exact prices not in provided data)",
    "search_addon": "bundled on Cloud, claimed 50-80% cheaper than Algolia/MeiliSearch",
    "volume_fees": "none claimed (B2B/distributor-friendly)",
    "notes": "Exact Cloud tier pricing not specified in provided content; pricing page should be fetched to normalize fully."
  },
  "issues": [
    "Cloud PaaS tier pricing is opaque from provided data — agents can't quote real costs without fetching medusajs.com/pricing/.",
    "No llms.txt content shown beyond intro — full agent-oriented content unknown, limiting agent self-onboarding confidence.",
    "auth_simplicity isn't max because self-hosted setup and Cloud account creation are decoupled; agent can't just 'sign in and go'.",
    "Platform spans self-hosted OSS and managed Cloud — dual nature adds description overhead and potential user confusion about which to recommend.",
    "Medusa MCP is beta, so agentic automation tooling is not yet production-stable."
  ],
  "recommendations": [
    "Publish structured pricing JSON at a stable URL (e.g., /pricing.json) so agents can quote tiers without HTML scraping.",
    "Expand llms.txt with explicit auth flows, API base URLs, and quickstart snippets to raise first_try_success.",
    "Offer magic-link or OAuth-based Cloud signup (or support 'Sign in with' verified identity) to push auth_simplicity toward 10.",
    "Clarify OSS-vs-Cloud decision criteria in docs so agents can recommend the right variant in one shot.",
    "Expose a status page endpoint and machine-readable changelog to strengthen consistency signal.",
    "Promote Commerce MCP from beta and document agent integration patterns explicitly."
  ]
}