Head to head · Commerce catalogues · October 2026 research run

Elastic Path API + MCP vs Swell

Swell scores 57 (C) on agent readiness against Elastic Path API + MCP's 56 (C), and leads in 3 of 7 scored categories. Elastic Path API + MCP leads on reliability and schema & documentation. Both do commerce catalogues.

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

Which one, for what

Elastic Path API + MCP C

Best for Enterprises already buying composable commerce who want an agent with broad back-office reach.

Ahead on

  • Reliability, 75 against 67
  • Schema & documentation, 83 against 71

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Swell loses 3 points for them

Watch for

MCP server exposes 95 tools with full CRUD, no read-only mode and no public source or licence

Swell C

Best for Developers who want a hosted headless store with a flexible data model and an agent that writes server-side.

Ahead on

  • Agent ergonomics, 65 against 41
  • Payments & pricing, 38 against 8
  • Maintenance & community, 82 against 77

Also in its favour

  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

One full-access secret key per environment, with no scoped or read-only key

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 Swell +30

Elastic Path API + MCP 8

No x402, MPP or L402 (0). The plan prices were read on 30 September from www.elasticpath.com, whose robots.txt now answers a Cloudflare bot check, so that reading is struck and no public price stands today (0). The developer docs link a Free Trial page, with no length or card terms we could read. Partly met, so the earlier 5 is kept (5 of 20). Contracts and trials go through a person (0). 0 + 0 + 5 + 0 = 5. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.

Swell 38

No x402, MPP or L402 (0). Plan prices are public with per-unit overage, $5 per extra 100K API requests and $5 per extra GB, plus 2 to 0.4 per cent above each sales ceiling (15). No free plan. A free trial on every plan, with the card requirement not stated (10). A person signs up in the browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Agent ergonomics Swell +24

Elastic Path API + MCP 41

The MCP server has 95 tools by its own npm description per the 30 September check, with no toolsets or filtering documented (5), and JSON:API includes let REST calls size responses a little (3). List operations take page[limit], page[offset] and filter in the OpenAPI files (20). The errors guide documents the JSON:API error array (status, title, detail) with example bodies for 400, 401, 403, 404, 409, 429 and 500, and a request ID on 500s. It is a generic guide that points to each call's page, and the bodies carry no error codes of their own, so the line is partly met and keeps its earlier 5 (5 of 20). No idempotency keys and no MCP annotations found (0). Official JavaScript SDK (36.1.0 on 26 October 2026) and generated @epcc-sdk packages, one language (8). 5 + 3 + 20 + 5 + 0 + 8 = 41.

Swell 65

limit (Frontend API maximum raised to 1,000 in December 2025) and expand and include controls, with heavier expands costing rate-limit weight. Field selection not confirmed (15). Page envelopes with count, page and page_count, plus where operators, sort and search (20). Validation errors carry a code per field, but invalid writes return HTTP 200 with an errors object, so an agent that doesn't check them reports success (15). No idempotency keys. Transactions roll back only on request errors, and there's no undo for merges (5). Official JavaScript libraries only (swell-node and swell-js), with simple Basic auth (10).

Schema & documentation Elastic Path API + MCP +12

Elastic Path API + MCP 83

Each API reference section has an Export OpenAPI Spec link to a downloadable OpenAPI 3.1 file, for example the Carts, Checkout, Orders file with 65 operations (25). llms.txt with about 1,050 lines, linking HTML pages rather than Markdown (10). Reference pages say what each endpoint does. We didn't read the 95 MCP tool descriptions, since the source isn't public (10). Typed REST parameters in the reference (11). Examples in the reference, and an errors guide with the JSON:API error shape and example bodies for 400, 401, 403, 404, 409, 429 and 500 (12 of 15). Dated changelog tagged MAJOR and MINOR, with deprecations carrying removal dates (15).

Swell 71

No OpenAPI file. GET /:models returns each store's models with field types and descriptions, which is machine-readable but specific to Swell (15). developers.swell.is/llms.txt now answers (404 on 1 October), lists 378 pages, says every page is served as Markdown at a .md address and links llms-full.txt (10). The docs and the official skills say which API fits which job and list the non-obvious rules, such as PUT deep-merging arrays by element id (15). Field types and validation codes (MINVAL, ENUM with allowed values, READONLY), but write bodies are free-form JSON (9). Status codes and validation objects documented with examples (13). Monthly dated changelog with no API versioning (9). 15 + 10 + 15 + 9 + 13 + 9 = 71.

Reliability Elastic Path API + MCP +8

Elastic Path API + MCP 75

Atlassian Statuspage at status.elasticpath.com with Admin API, Shopper API, Commerce Manager and Webhooks components for the EU and US regions per the 1 October check, and a history feed (20). The feed read on 4 November covers the whole window from 6 August. A proportion of US API requests saw elevated errors for 4 minutes on 21 September (EU unaffected), and Commerce Manager was degraded for 5 minutes on 1 October. Both are partial, so minor. Database maintenance on 13 October was scheduled maintenance, not an incident (20). Published limits of 100 requests a second for production stores and organisations and 50 for development stores (15). The rate-limits page documents 429 and says to wait a few seconds and retry, and the JS SDK retries in the browser. No Retry-After header or idempotency keys, so backoff guidance alone (10). No SLA found (0). The API and the Composable Commerce MCP server are generally available (10).

Swell 67

Atlassian Statuspage at status.swell.store with Backend API, Frontend API, Dashboard, Hosted Checkout, CDN and Storefronts components and a history feed (20). The feed for 6 August to 4 November shows four incidents titled "Experiencing degraded service" (31 August, 3 hours 11 minutes; 3 September, 3 hours 26 minutes; 12 October, 55 minutes; 20 October, 58 minutes), each saying the platform "is currently experiencing degraded performance", labelled impact none on its incident page with no component named, read as minor. Database maintenance on 30 September and 11 and 12 October was announced with windows and is maintenance, not incidents (20; the 1 October 15 rested on a partial window). Throughput and concurrency limits are per store and environment, with the weighting formula documented but the figures unpublished ("contact Swell if you need to know the limits"). Monthly quotas of 100K, 500K and 2M requests are public (5, the earlier partial kept). Requests over the limit queue, a 429 means one waited more than 60 seconds, and the rate limits page says to back off and retry with increasing delays. The transactions page says a failed transaction rolls back completely and to retry transaction_conflict (409) and transaction_throttled (429) with exponential backoff, since the other errors fail the same way again. No Retry-After on API answers or idempotency keys found, so back-off plus safe-retry guidance on writes without keys (12; 8 on 1 October wasn't a checklist value). The pricing page lists a "100% uptime SLA" on Unlimited, but robots.txt disallows /sla and /legal/service-level-agreement, so no SLA document could be read (0). Generally available (10). 20 + 20 + 5 + 12 + 0 + 10 = 67.

Maintenance & community Swell +5

Elastic Path API + MCP 77

Changelog entry on 2 November 2026 for Catalog Search API changes, 2 days before the check (30). Eleven dated API entries since 6 August, on 10 August (two), 27 August, 25 and 29 September, 6, 7, 21, 22 and 28 October and 2 November, with entries only about Commerce Manager screens left out (20). Public changelog with RSS, Atom and JSON feeds; support channel not checked (10). @elasticpath/js-sdk tagged 35.2.0 to 36.1.0 between 5 and 26 October 2026 (clone). The MCP on npm couldn't be re-read, and it isn't in the official registry (12). The MCP source isn't public, so its tests and CI can't be seen. The JS SDK's CI runs lint and build (5).

Swell 82

Re-read from depth-200 clones and the changelog on 4 November. swell-js v5.9.3 was tagged on 3 November 2026, the day before (30). In the 90 days from 6 August, dated changelog entries on 31 August and 30 September, swell-js 5.8.2 (24 September), 5.9.0 (28 September), 5.9.1 (29 September), 5.9.2 (7 October) and 5.9.3, and the official skills plugin from 0.7.0 (8 October) to 0.12.0 (2 November) (20). Monthly changelog and email and chat support on every plan (12, kept). swell-js is current; swell-node's last tag is still 6.0.5 from 18 May 2026. No Swell MCP server in the registry (12, kept). Test workflows in both SDK repositories (8). 30 + 20 + 12 + 12 + 8 = 82.

Score by category

CategoryWeightElastic Path API + MCPSwellEdge
Reliability16%7567Elastic Path API + MCP +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8371Elastic Path API + MCP +12
Agent ergonomics13%4165Swell +24
Security & auth14%4442Elastic Path API + MCP +2
Payments & pricing10%838Swell +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7782Swell +5
Transparency & trust7%6260Elastic Path API + MCP +2
Negative events≤150-3
TotalC 56/100C 57/100

Facts side by side

FactElastic Path API + MCPSwell
KindHTTP APIHTTP API
VendorElastic PathSwell
Hosted endpointhttps://useast.api.elasticpath.com/v2https://api.swell.store
TransportsHTTP, stdioHTTP
AuthOAuthAPI key
PricingPaidPaid
x402nono
Tools exposed95none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-292026-11-03
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be read2026-08-19
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity754 npm/wk4.5k npm/wk
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Swell higher.

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

Elastic Path API + MCP

Cart, promotion code, checkout and order endpoints cover the whole test flow, with downloadable OpenAPI files and a written 90-day deprecation notice. The MCP server exposes 95 tools with full CRUD, no read-only mode and no public source or licence, and no security programme was found.

Swell

Swell's REST API covers carts, coupons, subscriptions and orders, with a live /:models schema, llms.txt and Markdown docs, and a named sub-processor list. Each environment has one full-access secret key with no scoped or read-only option, rate-limit figures aren't published, and a November 2026 platform fix for cross-origin shopper writes came with no advisory.

Before you call either

Elastic Path API + MCP

  1. Use a client_credentials token server-side only. It has full CRUD on the store
  2. Pick the base URL for the store's region (useast or euwest), or every call returns 401
  3. Loading the MCP server costs 95 tool definitions, so enable it only for agents that need the back office
  4. On a 429, wait a few seconds and retry. No Retry-After header is sent
  5. Page list calls with page[limit] and page[offset], and read errors[].title and detail on failures

Swell

  1. Call GET /:models once and cache it. It's the ground truth for custom fields
  2. Check result.errors after every write. A failed validation still returns 200
  3. Use $set to replace an array. A plain PUT merges arrays by element id and never shrinks them
  4. Use an sk_test_ key while testing. A bare sk_ prefix is live
  5. Keep expand and include small. Each level past the first three points adds rate-limit weight

Questions

Which is better for AI agents, Elastic Path API + MCP or Swell?

Swell scores 57 (C) on agent readiness against Elastic Path API + MCP's 56 (C), and leads in 3 of 7 scored categories. Elastic Path API + MCP leads on reliability and schema & documentation.

Do Elastic Path API + MCP and Swell need an API key?

Elastic Path API + MCP uses an OAuth sign-in. Swell needs an API key.

Can an agent call Elastic Path API + MCP and Swell without installing anything?

Yes. Elastic Path API + MCP has a hosted endpoint at https://useast.api.elasticpath.com/v2 and Swell at https://api.swell.store.

Other comparisons with Elastic Path API + MCP or Swell

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.