Medusa
Medusa is an open-source headless commerce platform written in Node.js and TypeScript, distributed under the MIT license. The Medusa server exposes two REST APIs - a public Store API consumed by storefronts and end-customer clients, and a privileged Admin API consumed by the Medusa Admin dashboard and back-office tooling - both documented with OpenAPI. Around the server the project ships a modular Framework (API Routes, Modules, Module Links, Workflows, Subscribers, Scheduled Jobs, Admin Extensions), the Commerce Modules (cart, payment, customer, pricing, promotion, product, order, inventory, fulfillment, stock location, region, sales channel, tax, currency, API keys, user, auth), the @medusajs/js-sdk TypeScript client, the Medusa CLI (create-medusa-app), the Next.js storefront starter, a remote MCP server that exposes the docs to LLM coding assistants, and Medusa Cloud as an optional managed hosting offering with predictable per-environment pricing and no GMV fees.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Medusa the way a machine reads it — 58 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Medusa scores 41.9/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Medusa
Each block below is one kind of artifact we hold for Medusa. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Medusa JS SDK (@medusajs/js-sdk)
Official TypeScript / JavaScript SDK wrapping the Store and Admin REST APIs - typed clients, auth helpers, and ergonomic resource methods. Distributed via npm as @medusajs/js-sd...
Medusa Framework (Modules, Workflows, Routes)
Server-side framework primitives for extending Medusa - custom API Routes, Modules with their own data models (DML), Module Links, Workflows for transactional business logic, Su...
Medusa Commerce Modules
First-party domain modules that compose into a Medusa application - Cart, Payment, Customer, Pricing, Promotion, Product, Order, Inventory, Fulfillment, Stock Location, Region, ...
Medusa CLI (create-medusa-app)
Command-line tooling for scaffolding new Medusa projects, generating modules and migrations, running the server in dev, and managing common project tasks.
Medusa Next.js Storefront Starter
Reference Next.js storefront talking to the Medusa Store API - cart, checkout, account, product browse, payments, and search. Used as the canonical starting point for headless s...
Medusa Docs MCP Server
Remote Model Context Protocol server exposing the Medusa documentation to LLM-powered coding assistants - lets agents look up commerce modules, framework concepts, and APIs whil...
Medusa Core Repository
Monorepo with the Medusa server, Admin, Commerce Modules, Framework, and packages. MIT-licensed reference for self-hosting and for building modules and plugins.
Medusa Auth API
The Auth API from Medusa — 2 operation(s) for auth.
Medusa Carts API
The Carts API from Medusa — 3 operation(s) for carts.
Medusa Categories API
The Categories API from Medusa — 1 operation(s) for categories.
Medusa Collections API
The Collections API from Medusa — 1 operation(s) for collections.
Medusa Customers API
The Customers API from Medusa — 2 operation(s) for customers.
Medusa Orders API
The Orders API from Medusa — 2 operation(s) for orders.
Medusa Payments API
The Payments API from Medusa — 1 operation(s) for payments.
Medusa Products API
The Products API from Medusa — 2 operation(s) for products.
Medusa Regions API
The Regions API from Medusa — 2 operation(s) for regions.
Medusa Shipping API
The Shipping API from Medusa — 1 operation(s) for shipping.
Scroll within the panel for all 17 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Medusa Store API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Medusa Js Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Medusa Js Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Modular Commerce Modules
First-party domain modules (cart, order, product, inventory, pricing, promotion, payment, fulfillment, region, sales channel, tax, currency, auth) that can be swapped or extended.
Workflows Engine
Transactional, durable business-logic workflows with compensation steps for orchestrating multi-step commerce operations.
Admin Dashboard
Customizable React-based Medusa Admin UI with first-class admin extensions for adding screens, widgets, and routes.
Store and Admin REST APIs
Two distinct REST surfaces - public Store API and privileged Admin API - both described with OpenAPI.
JS / TypeScript SDK
Typed JS SDK (@medusajs/js-sdk) for both Store and Admin APIs with shared types from @medusajs/types.
Next.js Starter
Reference Next.js storefront wired to the Store API as a launchpad for custom storefronts.
CLI Tooling
create-medusa-app and the Medusa CLI for scaffolding projects, running dev servers, and managing migrations.
Agentic Development (MCP)
Remote MCP server exposing the docs and a Development Agent that lets LLM coding assistants build on Medusa.
Medusa Cloud
Optional managed hosting with GitHub-based deploys, autoscaling, and no GMV-based fees.
MIT License
Permissive open-source license with no vendor lock-in and the ability to self-host the full stack.
Scroll within the panel for all 10 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Headless DTC Storefronts
Power Next.js / React Native / native storefronts for direct-to- consumer brands using the Store API and JS SDK.
B2B Commerce
Build company-account, quoting, and approval flows on top of the Commerce Modules and Workflows engine.
Marketplaces
Use sales channels, regions, and stock locations to model multi- vendor and multi-store marketplaces.
Composable Commerce Replatforming
Replace Shopify, BigCommerce, or Magento with a fully owned, self-hostable commerce backend.
AI-Native Commerce
Drive merchandising, support, and operations from LLM agents using the MCP server and admin tooling.
Custom Checkout Experiences
Implement bespoke checkout, payment, and pricing flows by composing modules and workflows.
Quick Commerce & Logistics
Model stock locations, fulfillment, and regions for last-mile and on-demand delivery models.
Internal Commerce Platforms
Stand up an internal commerce backbone for catalog, orders, and fulfillment shared across brands or business units.
Scroll within the panel for all 8 ·
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Next.js
Official Next.js storefront starter (nextjs-starter-medusa) wired to the Store API.
Stripe
Payment provider integration for card payments and saved methods via the Payment module.
PayPal
PayPal payment provider integration via the Payment module.
Algolia / MeiliSearch / Typesense
Search integrations for product catalog indexing and storefront search.
SendGrid / Resend
Notification providers for transactional email through the Notification module.
AWS S3 / MinIO
File storage providers for product images and assets.
PostgreSQL
Primary supported database engine for the Medusa server.
Redis
Used for caching, event bus, and queues in production deployments.
Model Context Protocol (MCP)
Remote MCP server exposes the Medusa docs to Claude, Cursor, and other MCP-aware coding assistants.
GitHub
GitHub-based deployments and source-of-truth for Medusa Cloud environments.
Scroll within the panel for all 10 ·
Solutions 6
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Medusa Core (Self-Hosted)
Free, MIT-licensed open-source server, Admin, framework, and commerce modules deployable to any Node.js host.
Medusa Cloud - Develop
Entry managed tier with GitHub deploys, dev agent, and a shared server starting at $29/mo.
Medusa Cloud - Launch
Production-ready managed tier with autoscaling, custom domains, automatic backups, and zero-downtime deploys at $99/mo.
Medusa Cloud - Scale
Growth tier with background workers, priority support, and higher edge request quotas at $299/mo.
Medusa Cloud - Enterprise
SLA-backed enterprise tier with core-team access, custom agentic workflows, and implementation support.
Medusa Experts
Curated partner network of agencies and consultancies delivering Medusa implementations.
Resources
Every other property we hold for Medusa — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/medusa-js · machine-readable index on apis.io