Head to head · Commerce catalogues · October 2026 research run
Saleor API + MCP vs Swell
Saleor API + MCP scores 76.5 (BB) on agent readiness against Swell's 57 (C), and leads in every scored category. Both do commerce catalogues.
Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons
Which one, for what
Best for Teams that want an open-source GraphQL backend with multi-channel pricing and an agent that reads store data safely.
Ahead on
- Reliability, 75 against 67
- Schema & documentation, 89 against 71
- Agent ergonomics, 86 against 65
- Security & auth, 71 against 42
- Payments & pricing, 68 against 38
- Transparency & trust, 76 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- Open source
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
The MCP server can't create checkouts or orders
Swell C
Best for Developers who want a hosted headless store with a flexible data model and an agent that writes server-side.
Also in its favour
- A hosted endpoint, with nothing to install
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 Saleor API + MCP +30
Saleor API + MCP 68
No x402, MPP or L402 (0). Cloud plans are public, Select $1,599 a month to $200,000 GMV and Volume $3,999 to $1,000,000, with 0.8% and 0.4% overage, but there's no per-call or per-unit price (10). The BSD core is free to self-host, and Cloud sandboxes are free for non-commercial use with no card mentioned (20). An agent can run the core from the Docker image with no account, but Cloud needs a browser signup (15). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.
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.
Security & auth Saleor API + MCP +29
Saleor API + MCP 71
App tokens limited to named permissions such as MANAGE_PRODUCTS and MANAGE_ORDERS, revocable through the API, and short-lived staff JWTs with refresh. Tokens travel in headers, never the URL (27). The MCP server never runs mutations, and a self-run copy can pin allowed API domains with ALLOWED_DOMAIN_PATTERN (16). Tools return merchant- and shopper-entered text, marked openWorldHint, with no prompt-injection guidance found (5). Observability webhooks can report API calls, but no operator audit log of who did what was found (8). SECURITY.md routes reports through GitHub advisories or security@saleor.io, nine advisories were published between January and July 2026, and the pricing page lists SOC 2, PCI DSS and GDPR. No security.txt and no bounty (15).
Swell 42
One secret key per environment (test or live) with full access to every collection, revocable, plus public keys for the Frontend API (15). No scoped or read-only secret key found. Role-based permissions are listed only on the Unlimited plan (5). The API returns merchant- and shopper-entered content with no prompt-injection guidance found (5). An events audit log in the developer console shipped on 30 September 2026 (10). The Security and Privacy page at /legal/security, not found on 1 October, has a Vulnerability Reporting section asking reporters to email Swell, with no acknowledgement time, and states annual third-party penetration tests, encryption at rest and in transit, and breach notice within 72 hours. No security.txt (the path still redirects to itself), bug bounty or SOC 2 report; card processing is stated as on PCI DSS networks, not a Swell certification. A disclosure policy and route with no acknowledgement time is 7 (0 on 1 October). 15 + 5 + 5 + 10 + 7 = 42.
Agent ergonomics Saleor API + MCP +21
Saleor API + MCP 86
GraphQL field selection sizes every response, and the MCP server has 8 compact tools (25). Cursor pagination capped at 100, with filter, where, search and sort inputs (20). Mutations return typed errors with a code, field and message (18). Payment transaction mutations take an idempotencyKey, and 7 of the 8 MCP tools declare readOnlyHint and idempotentHint (the eighth only returns the API URL) (15). MCP tools default to 100 items and need only a channel. The official SDK is a TypeScript app SDK, with no general client in a second language (8).
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 Saleor API + MCP +18
Saleor API + MCP 89
One GraphQL schema with introspection, and a 954 KB SDL copy in the MCP repo (25). llms.txt split into per-section indexes (10). Fields and mutations carry descriptions, doc categories and deprecation reasons, but rarely say when not to use them (13). Strict GraphQL types with 78 error-code enums and required markers (14). Typed error codes on every mutation payload, with examples in the docs (12). CHANGELOG with a breaking changes section per minor version, GitHub releases, and 464 @deprecated markers in the schema (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.
Transparency & trust Saleor API + MCP +16
Saleor API + MCP 76
BSD-3-Clause core, with the MCP server under AGPL-3.0 (30). Privacy policy updated 8 August 2025 names Saleor Commerce sp. z o.o. in Wrocław, links a subprocessor list and states 30 days for cookies, but no DPA is linked from it and other retention is "not longer than necessary" (20). Deprecations are marked in the schema and removed in a named later version, with upgrade guides, but notices carry versions rather than dates (15). Self-hosted servers send daily usage telemetry by default (counts of products, attributes and models, plus version), described on a Usage Telemetry docs page and turned off with SEND_USAGE_TELEMETRY=False. Cloud subprocessors are listed (18).
Swell 60
Closed platform with published terms, and MIT SDKs and skills (15). The privacy policy, last modified 3 November 2026, gives retention only as long as necessary. The Data Processing Addendum linked from the security page commits to processing only on instructions, a purge after termination with a copy on request within 30 days, and a named sub-processor list. No retention periods by data type (20 of 30; 10 on 1 October before the DPA was read). No deprecation policy or dated notices found (0). The DPA names ten sub-processors with their purpose and headquarters (AWS, Google Cloud Platform and DigitalOcean for hosting, Cloudflare, Twilio, SolarWinds and others) and says EEA personal data is processed in the United States, with no hosting regions beyond that (16 of 20; 6 on 1 October). 15 + 20 + 0 + 16 = 51.
Reliability Saleor API + MCP +8
Saleor API + MCP 75
Graded on Saleor Cloud. Status page at status.saleor.io with an incident feed and history (20). One incident in the 90 days to 1 November, elevated GraphQL error rates, mostly 503s, for some EU stores from 18:01 to 18:23 UTC on 25 October, caused by an OIDC bug fixed in 3.23.45. Partial and 22 minutes, so minor (20). The usage limits page gives sandboxes 120 requests a minute on the free plan and 2,000 on paid plans, with production unlimited, plus a 50,000 query-cost cap, 100 items a page and 4 mutations per request (15). Requests over the limit get HTTP 429, and since 30 October the page says throttled production traffic also gets 429 and should be retried with backoff. Payment transaction mutations take an idempotencyKey, other writes don't, and no Retry-After is documented (10). No SLA on the pricing page (0). 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.
Score by category
| Category | Weight | Saleor API + MCP | Swell | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 67 | Saleor API + MCP +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 71 | Saleor API + MCP +18 |
| Agent ergonomics | 13% | 86 | 65 | Saleor API + MCP +21 |
| Security & auth | 14% | 71 | 42 | Saleor API + MCP +29 |
| Payments & pricing | 10% | 68 | 38 | Saleor API + MCP +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 82 | Saleor API + MCP +3 |
| Transparency & trust | 7% | 76 | 60 | Saleor API + MCP +16 |
| Negative events | ≤15 | -2 | -3 | |
| Total | BB 76.5/100 | C 57/100 |
Facts side by side
| Fact | Saleor API + MCP | Swell |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Saleor | Swell |
| Hosted endpoint | no (local only) | https://api.swell.store |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | BSD-3-Clause | none |
| Tools exposed | 8 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-11-03 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-08-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 23k stars, 7.3k npm/wk | 4.5k npm/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Saleor API + MCP higher.
| Reviewer | Saleor API + MCP | Swell |
|---|---|---|
| WardenSecurity auditor | 4/5 Read-only by design, with nine advisories behind it | 2/5 One key for every collection, and a day-old audit log |
| GullBrowser and end-to-end tester | 3/5 Eight tools to look, and raw mutations to buy | 3/5 Whole flow server-side, two traps that return 200 |
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
Saleor API + MCP
One GraphQL schema with 78 typed error-code enums and 464 marked deprecations. The MCP server can't create checkouts or orders.
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
Saleor API + MCP
- Pass the channel slug on product and checkout queries. Prices and availability are per channel
- Send X-Saleor-API-URL and X-Saleor-Auth-Token on every MCP request, with a token holding MANAGE_PRODUCTS and MANAGE_ORDERS
- Read the
errorsarray in every mutation payload. A 200 response can still carry a CheckoutErrorCode - Keep queries under the 50,000 complexity cap and 100 items a page, and send at most 4 mutations per request
- The 3.24 changelog removes the old dummy payment plugins, so test checkouts should use a payment app
- On a sandbox stay under 120 requests a minute (2,000 on paid plans), and retry an HTTP 429 with backoff
Swell
- Call GET /:models once and cache it. It's the ground truth for custom fields
- Check
result.errorsafter every write. A failed validation still returns 200 - Use
$setto replace an array. A plain PUT merges arrays by element id and never shrinks them - Use an sk_test_ key while testing. A bare sk_ prefix is live
- Keep
expandandincludesmall. Each level past the first three points adds rate-limit weight
Questions
Which is better for AI agents, Saleor API + MCP or Swell?
Saleor API + MCP scores 76.5 (BB) on agent readiness against Swell's 57 (C), and leads in every scored category.
Do Saleor API + MCP and Swell need an API key?
Saleor API + MCP takes an API key or an OAuth sign-in. Swell needs an API key.
Can an agent call Saleor API + MCP and Swell without installing anything?
No hosted endpoint is listed for Saleor API + MCP. Swell has a hosted endpoint at https://api.swell.store.
Are Saleor API + MCP and Swell open source?
Saleor API + MCP is open source (BSD-3-Clause). No open-source release is listed for Swell.
Other comparisons with Saleor API + MCP or Swell
- Adobe Commerce (Magento) vs Saleor API + MCP
- Adobe Commerce (Magento) vs Swell
- Agentzon vs Saleor API + MCP
- Agentzon vs Swell
- BigCommerce API + MCP vs Saleor API + MCP
- BigCommerce API + MCP vs Swell
- Commerce Layer API + MCP vs Saleor API + MCP
- Commerce Layer API + MCP vs Swell
- commercetools vs Saleor API + MCP
- commercetools vs Swell
- Ecwid by Lightspeed vs Saleor API + MCP
- Ecwid by Lightspeed vs Swell
- Elastic Path API + MCP vs Saleor API + MCP
- Elastic Path API + MCP vs Swell
- Medusa API + MCP vs Saleor API + MCP
- Medusa API + MCP vs Swell
- Saleor API + MCP vs Shopify API + MCP
- Saleor API + MCP vs Shopware
- Saleor API + MCP vs Snipcart API + MCP
- Saleor API + MCP vs Spree Commerce
- Saleor API + MCP vs Square
- Saleor API + MCP vs Vendure
- Saleor API + MCP vs Wix Stores and eCommerce API
- Saleor API + MCP vs WooCommerce API + MCP
- Shopify API + MCP vs Swell
- Shopware vs Swell
- Snipcart API + MCP vs Swell
- Spree Commerce vs Swell
- Square vs Swell
- Swell vs Vendure
- Swell vs Wix Stores and eCommerce API
- Swell vs WooCommerce API + MCP
- doola MCP vs Saleor API + MCP
- doola MCP vs Swell
- Fabric vs Saleor API + MCP
- Fabric vs Swell
Machine-readable
- This page as Markdown
/compare/saleor-vs-swell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/saleor.json·/api/v1/tools/swell.json - From a terminal
anchor compare saleor swell(the CLI) - Over MCP
compare_tools {"a": "saleor", "b": "swell"}at/mcp, no key