Medusa
Medusa is an open-source, MIT-licensed digital commerce platform built around a modular architecture: a suite of Commerce Modules (cart, products, orders, pricing, promotions, tax, inventory, fulfillment, payment), a Framework for building custom API routes, data models, workflows and integrations, and a customizable Medusa Admin dashboard. Medusa ships two first-party REST APIs — a Store API for storefronts and an Admin API for merchant operations — both documented with published OpenAPI 3.0 specifications generated from the codebase. Medusa is self-hosted by default; MedusaJS, Inc. also operates Medusa Cloud, a managed PaaS, and a remote MCP server plus published Claude Code agent skills for agentic development.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Medusa the way a machine reads it — 91 machine-readable artifacts across 2 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 62.7/100 (strong), with a separate agent-readiness read of 56/100 (agent native). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Medusa's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/medusa/"
title="Medusa on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/medusa.svg"
alt="Medusa Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/medusa/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/medusa/"
title="Medusa on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/medusa/card.svg"
alt="Medusa Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 82
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 GraphQL API
Medusa's GraphQL surface over the store data core. The schema in this repo was derived from the OAS output schemas published in the medusajs/medusa repository; Medusa does not p...
Medusa MCP Remote Server
Medusa hosts a Streamable HTTP Model Context Protocol server at https://docs.medusajs.com/mcp. It exposes the Medusa documentation to coding agents plus curated implementation-g...
Medusa Api Keys API
API keys can be used for authentication or resource-scoping. A secret API key can be used to authenticate admin users. A publishable API key can be used to scope client requests...
Medusa Auth API
Auth API routes allow you to manage an admin user's authentication.
Medusa [auth Provider] API
The [auth_provider] API from Medusa — 1 operation(s) for [auth_provider].
Medusa Campaigns API
A campaign is a group of promotions that have the same conditions, such as start and end dates. These API routes allow admin users to manage campaigns, their conditions, and pro...
Medusa Carts API
A cart is a virtual shopping bag that customers can use to add items they want to purchase. A cart is then used to checkout and place an order. These API routes allow customers ...
Medusa Claims API
An admin creates a claim for an order when a customer reports that an item is defective or incorrect. Using these API routes, admin users manage order claims, their items, and m...
Medusa Collections API
A product collection organizes products into a collection for marketing purposes. For example, a summer collection. These API routes allow admin users to manage collections and ...
Medusa Currencies API
A store can use unlimited currencies, and each region must be associated with at least one currency. Currencies are defined by the Currency Module. Currency API Routes allow adm...
Medusa Customer Groups API
Customers can be organized into groups. These groups are useful for segregation and marketing purposes. For example, you can provide different prices for specific customers by c...
Medusa Customers API
Customers can either be created when they register through the Store APIs, or created by the admin using the Admin APIs. These API routes allow admin users to manage customers i...
Medusa Draft Orders API
A draft order is an order created by the admin user. This is useful for orders created offline or from clients other than a storefront, such as a third-party integration. These ...
Medusa Exchanges API
An exchange is the replacement of an item that the customer ordered with another. These API routes allow admin users to create and manage exchanges.
Medusa Feature Flags API
Feature flags are used to enable or disable certain features in your Medusa application. These API routes allow admin users to view feature flags.
Medusa Fulfillment Providers API
A fulfillment provider is a third-party integration or custom logic used to fulfill an order's items. Fulfillment providers are installed as module providers.
Medusa Fulfillment Sets API
A fulfillment set is a general form or way of fulfillment, such as "shipping" or "pick up". All fulfillment-related configurations in a store are related to a fulfillment set. T...
Medusa Fulfillments API
A fulfillment is created for items in an order, return, exchanges, or claims to deliver items to/from the customer. These API routes allow admin users to manage fulfillments.
Medusa Gift Cards API
A gift card is a prepaid card that can be used to pay for items during checkout. Gift cards can be purchased by customers, or created by admin users. When a gift card is redeeme...
Medusa Index API
The Index Module is a tool to perform high-performance queries across modules, for example, to filter linked modules. The Index Module is currently experimental and is hidden be...
Medusa Inventory Items API
An inventory item is a stock-kept product whose inventory is managed. These API routes allow admin users to manage inventory items.
Medusa Invites API
An admin can invite new users to manage their team. This allows new users to authenticate as admins and perform admin functionalities. These API routes allow admin users to mana...
Medusa Layouts API
An admin can modify the layout of their admin dashboard. This allows admins to customize their dashboard to their preferences and needs. These API routes allow admin users to ma...
Medusa Locales API
A locale is a language that content is translated into for customers to view in a storefront. Medusa installs locales by default. These API routes allow admin users to retrieve ...
Medusa Multi-Factor Authentication API
Multi-factor authentication (MFA) adds an extra layer of security to admin accounts by requiring additional verification factors during login, such as a TOTP code or a recovery ...
Medusa Multi-Factor Authentication (MFA) Factors API
Multi-factor authentication (MFA) factors are additional ways to verify a customer's identity during login, in addition to their password. Examples of MFA factors include authen...
Medusa Notifications API
A notification informs an admin user of store changes or status changes of background tasks. These API routes allow admin users to view and manage notifications.
Medusa Order Changes API
An order change is a proposed change to an order, such as adding or removing items, changing shipping methods, and more. They can be associated with order edits, claims, or exch...
Medusa Order Edits API
An order edit is a change to an order's details, such as items, shipping methods, and more. Changes made by an order edit are only applied on the order once they're confirmed. T...
Medusa Orders API
An order is a purchase made by a customer through a storefront. Orders can also originally be created as draft orders. These API routes allow admin users to view and manage orders.
Medusa Payment Collections API
A payment collection is one or more payments of an order. They're also used for outstanding payments due to order exchanges or claims. Every purchase or request for payment star...
Medusa Payment Providers API
Each region has a set of payment providers enabled. During checkout, you retrieve the available payment providers in the customer's region to show them to the customer. Customer...
Medusa Payments API
A payment is created when a payment amount is authorized. The payment can then be captured or refunded. A payment is created from the payment session that was authorized, and it...
Medusa Plugins API
A plugin is a package of reusable Medusa customizations that you can install in any Medusa application. Plugins can be used to add new functionality, such as wishlists, or integ...
Medusa Price Lists API
A price list is a group of prices applied if the specified conditions and rules are satisfied. Price lists are useful for sales or special prices for special conditions, such as...
Medusa Price Preferences API
A price preference is used to specify whether tax-inclusiveness is enabled for a context, such as a region or currency code. These API routes allow admin users to manage whether...
Medusa Product Categories API
Products can be categorized into categories. Categories are nested and their heirarchy can be managed, giving admin users flexibility in how they categorize their products. Thes...
Medusa Product Options API
A product option is a way to define different options for a product, such as "Size" or "Color". Product options can be created globally and used by multiple products, or they ca...
Medusa Product Tags API
A tag is another way of organizing a product. Each tag has a name and a value. Products are organized into the same tag if they have the same value. These API routes allow admin...
Medusa Product Types API
Products can be organized into types. Each type has a name and a value. Products are organized into the same type if they have the same value. These API routes allow admin users...
Medusa Product Variants API
A product variant is a saleable form of the product. Each variant has different option values. For example, a "Shirt" product may have a "Blue" variant and a "Green" variant. Cu...
Medusa Products API
A product is a set of variants that the customer chooses from when making a purchase. A product can be organized into categories or collections. A product can have many options,...
Medusa Promotions API
A promotion discounts an amount or percentage off a cart's items, shipping methods, or the entire order. Promotions have different types, such as a `standard` promotion that jus...
Medusa Property Labels API
The Property Labels API from Medusa — 3 operation(s) for property labels.
Medusa Refund Reasons API
A refund reason is a possible reason used when issuing a refund to the customer, such as when returning an item and refunding the customer. These API routes allow admin users to...
Medusa Regions API
Regions are different countries or geographical regions that the commerce store serves customers in. These API routes allow admin users to manage regions, their providers, and m...
Medusa Reservations API
A reservation is unavailable quantity of an inventory item in a location. A reservation is created automatically for variants in an order whose `manage_inventory` is enabled. Ad...
Medusa Return Reasons API
A return reason is a possible reason that an item is returned from the customer, such as when returning an item. These API routes allow admin users to manage return reasons.
Medusa Returns API
Admin users create a return when a customer returns an item to them. Returns can also be created by customers through the storefront, and admins will be able to manage them and ...
Medusa Sales Channels API
A sales channel indicates a channel where products can be sold in. For example, a webshop or a mobile app. These API routes allow admins to manage sales channels and the product...
Medusa Search API
The Search API from Medusa — 1 operation(s) for search.
Medusa Shipping Option Types API
Shipping option types define a group of shipping options with shared shipping characterstics. For example, you may have "Standard" and "Express" shipping option types. These API...
Medusa Shipping Options API
A shipping option is a way of shipping an item to or from the customer. Shipping options are associated with the fulfillment provider used to handle their fulfillment. Shipping ...
Medusa Shipping Profiles API
A shipping profile defines a type of items that are shipping in a similar manner. For example, digital products may have a `digital` shipping profile. These API routes allow adm...
Medusa Stock Locations API
A stock location is where stock-kept items (products) are kept. Stock locations are linked to fulfillment providers used to fulfill items from this location. A stock location is...
Medusa Store Credit Accounts API
A store credit account is a ledger of store credit transactions for a customer. They hold the customer's store credit balance, including their credit and debit amounts. Store cr...
Medusa Stores API
A store holds the main configuration and information of your commerce store, such as supported currencies or default sales channel. By default, the Medusa application has one de...
Medusa Tax Providers API
A tax provider is a third-party integration or custom logic used to calculate taxes for a cart or an order. These API routes allow admin users to manage tax providers installed ...
Medusa Tax Rates API
A tax rate is a percentage amount used to calculate the tax amount of each taxable item's price, such as line items or shipping methods. Each tax region has a default tax rate. ...
Medusa Tax Regions API
A tax region is a region's tax settings. It has tax rates and rules. So, after you create a region, you must create a tax region for it. A tax region can extend settings from a ...
Medusa Translations API
A translation is a localized version of content in a specific locale. For example, a product description in French. These API routes allow admin users to manage translations for...
Medusa Uploads API
Use these API routes to upload files to your Medusa application using the installed file module provider. You can upload public files, such as product images, or private files, ...
Medusa Users API
A user is an admin user that can authenticate and perform functionalities as an admin user. An admin user can invite other users to join their team. Once they accept the invite,...
Medusa Views API
A view configuration is a saved data-table view for an entity, such as products or orders. It lets admin users customize how a table shows its data, then save that customization...
Medusa Workflows Executions API
These API routes allow you to track workflow executions in your Medusa application. Depending on the workflow engine you use, executions may only be retained for a short while, ...
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 82 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Medusa MCP Server
Medusa operates one official MCP server. It is REMOTE ONLY — a Streamable HTTP endpoint at https://docs.medusajs.com/mcp. There is no npm/stdio package: @medusajs/mcp does not e...
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Medusa GraphQL API
Medusa is an open-source headless commerce platform with a modular architecture that enables developers to build custom commerce applications. The GraphQL API exposes the full s...
GRAPHQLPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Medusa Plans Pricing
PLANSRate 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 Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Medusa Events
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/medusa · machine-readable index on apis.io
This is an independent, third-party profile of Medusa, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.