# Medusa

**Canonical:** https://apis.io/providers/medusa-js/  
**Website:** https://medusajs.com/  
**APIs profiled:** 17

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.

## Kin Score — 40.7 / 100 (developing)

Scored 2026-08-25 under rubric 0.14.0. Trend: flat (+0.0 from 40.7).

| Facet | Score |
|---|---|
| Discoverability | 81.5 |
| Contract Quality | 44.2 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 50.0 |
| Developer Ergonomics | 35.7 |
| Commercial Clarity | 39.5 |
| Access Clarity | 39.5 |

## Agent readiness — 19.8 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | bearer |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |

## Access

Free · Self-serve signup — onboarding: self-serve, pricing: free, trial: no (confidence: high).

## APIs (17)

- **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.

## Agentic access (1)

- **Medusa Js Agentic Access** — 18 operations · 7 acting

## Security (2)

- **Medusa Js Authentication** — apiKey/http · 3 schemes
- **Medusa Js Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC

## Plans (1)

- **Medusa Js Plans Pricing**

## Use cases (8)

- **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.

## Tags

Commerce, Headless, E-Commerce, Open-Source, Node.js, TypeScript, Framework, Modules, Workflows, MCP

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/medusa-js/). Scores are computed from the provider's own public artifacts under a published rubric.