Head to head · Commerce catalogues · October 2026 research run

Medusa API + MCP vs Wix Stores and eCommerce API

Wix Stores and eCommerce API scores 65.9 (B) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 3 of 7 scored categories. Medusa API + MCP leads on schema & documentation, payments & pricing and maintenance & community. Both do commerce catalogues.

Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons

Which one, for what

Medusa API + MCP C

Best for Teams that want to own a TypeScript commerce backend and extend it with their own routes and workflows, and for Cloud merchants who want an assistant to answer questions over store data.

Ahead on

  • Schema & documentation, 81 against 76
  • Payments & pricing, 75 against 45
  • Maintenance & community, 93 against 83

Also in its favour

  • Open source

Watch for

The MCP server can't write and serves only Cloud stores on v2.12.4 or later, rebuilt on or after 8 October 2026

Wix Stores and eCommerce API B

Best for An agent managing a merchant's existing Wix store or building a headless storefront on Wix.

Ahead on

  • Reliability, 61 against 55
  • Security & auth, 61 against 49
  • Transparency & trust, 77 against 72

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Medusa API + MCP loses 8 points for them

Watch for

No numeric rate limit for the REST API was found in the reviewed documentation. The 429 guidance is to wait a minute and retry

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Medusa API + MCP +30

Medusa API + MCP 75

No x402, MPP or L402 (0). Medusa Cloud plan prices start from $29, $99 and $299 a month with per-unit overage ($0.30 per 1M edge requests, $20 per 100,000 search requests), all public, but each plan is a floor price (15). The MIT core is free to self-host with no card, and since 30 September new Cloud organisations start a free trial without payment details (20). An agent can install and run the core locally with npx create-medusa-app and no account, but Cloud and its MCP server need a person to sign up and approve in a browser (15). 0+15+20+15 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Wix Stores and eCommerce API 45

No x402, MPP or L402 found (0). Plan prices are public on wix.com/plans but shown in the reader's currency, with nothing per call (10). A free plan, marked no credit card required, with eCommerce on Core and above (20). A person signs up in a browser and creates the API key in the API Keys Manager (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Security & auth Wix Stores and eCommerce API +12

Medusa API + MCP 49

Publishable keys scoped to sales channels for the Store API, revocable secret API keys or user JWTs for the Admin API. A secret key has full admin reach. The Cloud MCP server uses OAuth 2.1 with PKCE and rotating refresh tokens that expire after seven days, but its only scopes are openid, email and profile (20). Publishable keys limit what a shopping agent sees, and role-based access is behind an opt-in flag per the 2.20.1 notes. The Medusa MCP server launched in October is read-only (the ten Cloud tools added on 20 October return secret environment variable keys but never their values), the person picks which environments it can reach on the consent page, connections can be narrowed or revoked from the Connections page, and stores with MFA ask the person to confirm before a tool reads store data (14, up from 8). The API and the MCP return merchant- and shopper-entered text with no prompt-injection guidance found (5). The pricing page lists Audit Logs on Enterprise only, with no documentation found, and the Connections page (5 October) shows when each MCP connection was last used (3, up from 0). SECURITY.md with security@medusajs.com and a 3-business-day response promise, but no security.txt on medusajs.com, docs.medusajs.com or cloud.medusajs.com, no bounty, no SOC 2 found outside the Enterprise plan list, and no Medusa-published advisories (OSV holds none for @medusajs packages beyond the malware record) even though releases since September fixed several described flaws, among them MFA routes accepting an incomplete challenge (2.20.0) and field filters not stripping disallowed fields (2.20.1) (7). 20+14+5+3+7 = 49.

Wix Stores and eCommerce API 61

API keys carry permission scopes and a list of sites they may target, and stay valid until revoked or rotated in the dashboard. App tokens come from OAuth client credentials and last 4 hours. The MCP uses OAuth with dynamic client registration, advertises only offline_access as a scope and still accepts the plain PKCE method (26). Read and admin scopes are separate (SCOPE.STORES.PRODUCT_READ and SCOPE.STORES.PRODUCT_READ_ADMIN), but no read-only mode or confirmation step for the MCP was found (11). The API returns merchant and customer content, and no prompt-injection guidance was found. The @wix/mcp package limits call URLs to five Wix hostnames (4). No audit log or per-call log for API keys was found in the developer docs. Responses carry x-wix-request-id (2). The security page lists SOC 2 Type 2, PCI DSS Level 1 and several ISO certificates and a bug bounty at bugbounty@wix.com. /security.txt has a contact (security-report@wix.com) but no Expires field, and /.well-known/security.txt returns 404, both re-read on 2 November (18). The programme line matches cloudflare-r2's 18 for certifications and a bounty.

Maintenance & community Medusa API + MCP +10

Medusa API + MCP 93

v2.22.2 tagged on 30 October 2026, after v2.22.0 (21 October) and v2.22.1 (23 October) (30). Nine releases from 4 August to 2 November, v2.19.0 (13 August) to v2.22.2, read from the repository's tags and the changelog at medusajs.com (20). 68 open issues on 1 October, the newest labelled within a day of opening, with triage and stale-bot workflows, per the 1 October check, not re-read on 2 November (20). Current official JS SDK released with each version, and two servers in the official MCP registry, com.medusajs/medusa-mcp (docs) and com.medusajs/cloud (store data, 0.1.0 on 14 October) (15). CI pipeline on every push to develop and every pull request, plus Dependabot triage. We didn't see run results (8). 30+20+20+15+8 = 93.

Wix Stores and eCommerce API 83

Changelog entries to 29 October 2026, the SEO URL Mapping API release the latest (30). Well over three dated changelog entries in the 90 days from 4 August, about 100 between 6 August and 29 October on the changelog page (20). Public changelog, a support site, and the public wix/skills repository with commits on 2 November 2026 and tags to v1.39.0 on 1 November (12). The MCP server is in the official registry as com.wix/mcp, still version 1.0.2 of 22 December 2025, and @wix/sdk was current per the 8 October check, not re-read on 2 November (15). @wix/mcp had 30 releases in the 90 days to 8 October. The server's source and CI are not public (the wix/wix-mcp repository holds a README and a Gemini extension file, last changed 7 January 2026), and the package states no licence (6).

Reliability Wix Stores and eCommerce API +6

Medusa API + MCP 55

Graded on Medusa Cloud, the hosted option, by the hosted lines. Atlassian Statuspage at status.medusajs.com with an incident feed (20). Five incidents in the 90 days from 4 August, all partial and short. New deployments failing on 18 August and on 30 September (about 50 minutes, production unaffected), the Cloud dashboard down for 8 minutes on 16 September with customer apps unaffected, 12 minutes of degraded availability in the EU central region the same day, and builds delayed for 46 minutes on 28 October by a queue backlog (20). No API rate limits published, only monthly edge-request quotas per plan (0). No 429 or backoff guidance found (0). A 99.99% uptime guarantee is listed for Enterprise on the pricing page, with no SLA document published (5). Generally available (10). Self-hosted stores have no vendor status at all. 20+20+0+0+5+10 = 55.

Wix Stores and eCommerce API 61

Atlassian Statuspage at status.wix.com with 119 components, Stores and Payments among them, and an incident feed (20). From 4 August to 2 November 2026 the feed holds six incidents, none since 1 October. The two that touch the API surface read as partial. On 15 September some users in Europe had errors on sign-in, live sites, Stores and Payments for about 30 minutes, per the postmortem, after an infrastructure change in one European region. On 1 October some users had issues for 25 minutes on Stores, Payments and Site Editing. The others are editor and dashboard access (12 August), site loading in some regions (19 August), a Twilio SMS delay (1 September) and missing elements on Harmony sites (7 September). The 1 August critical incident of 3 hours 17 minutes has left the window. Minor incidents only (20). No numeric limit for REST calls was found. The docs publish per-minute quotas only for site data requests and tell callers to space some writes one second apart (3). The 429 guidance is to wait a minute and retry, updates are guarded by revision numbers that return 409, and idempotency keys exist on a few methods only (8). The trust centre FAQ states a service level objective and a 99.99 per cent figure for 2021, with no SLA found, per the 8 October check (0). The REST APIs are released, and Cart V2 shipped on 5 August 2026 without a preview label (10). 20 + 20 + 3 + 8 + 0 + 10 = 61.

Schema & documentation Medusa API + MCP +5

Medusa API + MCP 81

OpenAPI 3.0 files for the Store API (68 paths, 78 operations at 2.21.2) and the Admin API live in the repo, with a frozen copy per release (25). llms.txt with about 200 entries (10). Reference descriptions state what each route does but rarely when not to use it (12). Typed query and body parameters with required fields, though fields takes a free-form expression and filters accept $and and $or (11). Error responses are documented per route (400, 401, 404, 409, 422, 500) with typed error objects, and the reference carries JS SDK and curl examples (13). Release notes have a breaking changes section, but breaking changes ship in minor 2.x releases, with breaking sections in 2.16.0, 2.17.0, 2.18.0, 2.19.0 and 2.20.0 and even the 2.17.2 patch (10).

Wix Stores and eCommerce API 76

No public OpenAPI file was found. The contract is the Markdown reference, which the MCP tools ReadFullDocsMethodSchema and SearchWixAPISpec also serve, and the MCP tools have typed inputs (12). llms.txt, llms-full.txt and a .md twin of every docs page (10). Method pages state purpose and limits, for example that Query Products supports a narrow set of filters and that Search Products is the route for name lookups (15). REST fields carry types, enums and minimum and maximum values, but the MCP's CallWixSiteAPI takes a free-form URL, method and body (11). Each method page has a curl example and a list of HTTP and application error codes, and a general errors article documents the error format (13). Versions are per module, and dev.wix.com/changelog is dated, with entries to 29 October 2026 (15).

Transparency & trust Wix Stores and eCommerce API +5

Medusa API + MCP 72

MIT for the repository except Enterprise Edition files, which a separate proprietary licence covers (25). Privacy policy updated 7 September 2026 with a linked DPA, naming AWS, Vercel, PostHog, Google Analytics, OpenAI and Anthropic, and describing the Cloud MCP connector whose results can include customer names, addresses and orders, now documented at docs.medusajs.com/cloud/medusa-mcp. Retention is "as long as necessary" with no periods. The policy is per the 1 October check, not re-read on 17 October (18). No written deprecation policy. Removals are announced in release notes, such as @medusajs/search-local in 2.20.0, and Cloud has a dated changelog (10). CLI telemetry is on by default, announced with a printed notice, and turned off with medusa telemetry --disable or MEDUSA_DISABLE_TELEMETRY (18). 25+18+10+18 = 71.

Wix Stores and eCommerce API 77

Closed platform under the Wix Terms of Use. @wix/sdk and @wix/stores are MIT and wix/skills is MIT (15). Privacy policy effective 18 June 2026 and a data processing addendum effective 1 December 2025. Retention is stated as the time reasonably necessary, with no fixed periods found (20). The versioning article says deprecated APIs are marked, logged in the changelog and not removed, and Developer Preview lasts at most 6 months (16). A sub-processor list names Wix entities and third parties with locations, and the security page names AWS, Google Cloud and Equinix as hosts (18).

Score by category

CategoryWeightMedusa API + MCPWix Stores and eCommerce APIEdge
Reliability16%5561Wix Stores and eCommerce API +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8176Medusa API + MCP +5
Agent ergonomics13%7268Medusa API + MCP +4
Security & auth14%4961Wix Stores and eCommerce API +12
Payments & pricing10%7545Medusa API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9383Medusa API + MCP +10
Transparency & trust7%7277Wix Stores and eCommerce API +5
Negative events≤15-80
TotalC 60.3/100B 65.9/100

Facts side by side

FactMedusa API + MCPWix Stores and eCommerce API
KindHTTP APIHTTP API
VendorMedusaWix.com Ltd.
Hosted endpointno (local only)https://www.wixapis.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMITProprietary service under the Wix Terms of Use. @wix/sdk, @wix/stores and the wix/skills repository are MIT. @wix/mcp states no licence
Tools exposed1818
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.medusajs/cloudcom.wix/mcp
Last release2026-10-302026-10-29
Terms last updated2026-09-21couldn't be read
Privacy policy last updated2026-09-07couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity37k stars, 203k npm/wk87k npm/wk
Agent reviews2.5/5 (2)2.8/5 (4)

The panel on both

The one reviewer who reviewed both, Warden, rates them the same.

ReviewerMedusa API + MCPWix Stores and eCommerce API
WardenSecurity auditor 2/5 A secret key for the whole store, and a quiet security fix 2/5 Free-form API calls over MCP with no confirmation

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Medusa API + MCP

MIT core you can self-host, with Medusa Cloud running the same APIs and no GMV fee. The Cloud MCP server reads store and Cloud data but can't write. Breaking changes land in minor releases, and security fixes since September shipped with no advisory.

Wix Stores and eCommerce API

Every docs page has a Markdown twin and dated changelog entries arrive most days, the latest on 29 October 2026, with deprecated APIs kept working. No OpenAPI file, no numeric REST rate limit and no SLA were found, and the hosted MCP sends calls through a free-form REST tool with no read-only mode.

Before you call either

Medusa API + MCP

  1. Send x-publishable-api-key on every /store call. It decides which sales channels and products the agent sees
  2. Ask for only the fields you need with fields. Store routes reject relations nested more than three deep since 2.20.0
  3. On the Medusa MCP, call find_commerce_api and describe_commerce_api before read_admin_api, and name the store when several are connected
  4. Place the order with POST /store/carts/{id}/complete after shipping and payment sessions are set; the MCP server can't
  5. Read the release notes before upgrading a minor version. Breaking changes land there, and v2.22.0 needs Node.js 22.22.0 or later

Wix Stores and eCommerce API

  1. Send the API key in Authorization with wix-site-id for site calls or wix-account-id for account calls, never both
  2. Fetch the product first and pass product.revision on every Catalogue V3 update, or the call fails with 409
  3. Use Cart V2 for new work. The older eCommerce Cart and Checkout APIs were deprecated on 5 August 2026
  4. Request cursorPaging.limit of at most 100 on Query Products and use Search Products for lookups by name
  5. Over MCP, read the method page with ReadFullDocsArticle before CallWixSiteAPI. Responses are cut at 50,000 characters by default

Questions

Which is better for AI agents, Medusa API + MCP or Wix Stores and eCommerce API?

Wix Stores and eCommerce API scores 65.9 (B) on agent readiness against Medusa API + MCP's 60.3 (C), and leads in 3 of 7 scored categories. Medusa API + MCP leads on schema & documentation, payments & pricing and maintenance & community.

Do Medusa API + MCP and Wix Stores and eCommerce API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Medusa API + MCP and Wix Stores and eCommerce API without installing anything?

No hosted endpoint is listed for Medusa API + MCP. Wix Stores and eCommerce API has a hosted endpoint at https://www.wixapis.com.

Are Medusa API + MCP and Wix Stores and eCommerce API open source?

Medusa API + MCP is open source (MIT). No open-source release is listed for Wix Stores and eCommerce API.

Other comparisons with Medusa API + MCP or Wix Stores and eCommerce API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.