Head to head · Commerce catalogues · October 2026 research run
Swell vs Vendure
Vendure scores 72.3 (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
Swell C
Best for Developers who want a hosted headless store with a flexible data model and an agent that writes server-side.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
One full-access secret key per environment, with no scoped or read-only key
Vendure BB
Best for TypeScript teams that want a typed GraphQL commerce server and will host it.
Ahead on
- Reliability, 89 against 67
- Schema & documentation, 91 against 71
- Security & auth, 65 against 42
- Payments & pricing, 75 against 38
- Transparency & trust, 74 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- Open source
- Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
Watch for
No vendor-hosted API. Vendure Cloud is in a closed beta for paid subscribers
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 Vendure +37
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.
Vendure 75
No x402, MPP or L402 (0). Core is free. Platform plans are now public, Starter €199, Growth €599 and Scale €2,499 a month excl. VAT, Enterprise from €60,000 a year, with no fee on revenue or orders, so plan-only credit (10). Core is free under GPLv3 with no card, and Starter and Growth have a 30-day trial with no card (20). An agent can scaffold a store with npx @vendure/create or query the public read-only demo Shop API without an account (20). 0+10+20+20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Security & auth Vendure +23
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.
Vendure 65
API keys since 3.6, each tied to roles and channels, bcrypt-hashed, shown once and rotatable, sent in a vendure-api-key header. Since 3.7.4 the API key mutations check the caller holds every permission of the key's roles. No OAuth in the GraphQL APIs; the MCP plugin uses OAuth 2.1 (28). Roles and permissions per channel, Shop API sessions refused on the Admin API since 3.8.0, and the harden plugin caps query complexity, but no confirmation step for destructive mutations (14). Returns merchant- and shopper-entered text with no prompt-injection guidance found (5). The MCP plugin released in 3.8.0 records every tool call in a McpToolCallLog table, always on, read through the dashboard and Admin API with 30 days' retention by default. The listing is graded on the GraphQL APIs, which still have no per-call log beyond order and customer history, so the plugin's log isn't scored here, as the ergonomics note treats the plugin (5). SECURITY.md takes private reports through GitHub and supports only the latest 3.x minor. Advisories are published with each release, 11 in 3.7.3, two in 3.7.4, one in 3.8.0 and three in 3.8.1. No security.txt (404), bounty or certification found (13). 28+14+5+5+13 = 65.
Reliability Vendure +22
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.
Vendure 89
Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in a closed beta for paid subscribers, general availability planned for Q1 2027). @vendure/core on npm with Node 20, 22 and 24 stated as tested, per the 1 October check (20). Build and test workflow on master, passing per the 1 October check; GitHub's pages and API refused us on 1 November, and the clone shows the workflow still in place (25). 170 open issues per the 1 October check, not re-read on 1 November. 3.8.1 fixes the 9 September stale-surcharge bug among 33 fixes (17). Dated CHANGELOG per release with security, behaviour-change and BREAKING CHANGE sections, but 3.7.3 and 3.7.4 changed behaviour in patch releases to close security holes and 3.8.0 is a minor release that needs a database migration (12). Version 3.x (15). 20+25+17+12+15 = 89.
Schema & documentation Vendure +20
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.
Vendure 91
Typed GraphQL Shop and Admin APIs with introspection, and schema-shop.json and schema-admin.json committed to the repo (25). llms.txt at docs.vendure.io, 997 lines on 1 November, including the MCP server guides (10). Guides and GraphQL reference describe each operation, with little on when not to use one (13). Strict GraphQL input types with enums and required markers (14). Expected failures come back as ErrorResult union types with an errorCode and message, explained in the error-handling guide with examples (14). Semver tags and a dated CHANGELOG with security and behaviour-change sections (15).
Transparency & trust Vendure +14
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.
Vendure 74
GPL-3.0-or-later, with a commercial licence sold through Platform (30). Terms of Service and Privacy Policy, both version 2026-10-20, name Elevantiq GmbH trading as Vendure. The policy lists processors with locations (WorkOS, Amazon SES in Frankfurt, Vercel, Northflank in Frankfurt, Plausible, Sentry in the EU and others) and retention by category, such as 7 days for package download records and 12 months for licence-check IP addresses. Section 16 of the terms is a data processing agreement under Article 28 GDPR for support access on the self-serve plans, Vendure Cloud has its own, and the subprocessor list for that processing is given on request rather than published (25). SECURITY.md says only the latest 3.x minor gets fixes, and deprecations appear in the changelog without dated end-of-life notices (10). Core sends anonymous usage telemetry on by default since 3.6.0, at startup and about every 24 hours, to telemetry.vendure.io. The telemetry guide lists the fields (installation ID, versions, database type, plugin names, ranged entity counts), and VENDURE_DISABLE_TELEMETRY or a CI environment turns it off. Licence reports from Platform's commercial plugins don't follow that switch, which the terms say (20). The 1 October note said no usage telemetry was found in core, which was wrong. 30+25+10+20 = 85.
Score by category
| Category | Weight | Swell | Vendure | Edge |
|---|---|---|---|---|
| Reliability | 16% | 67 | 89 | Vendure +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 71 | 91 | Vendure +20 |
| Agent ergonomics | 13% | 65 | 68 | Vendure +3 |
| Security & auth | 14% | 42 | 65 | Vendure +23 |
| Payments & pricing | 10% | 38 | 75 | Vendure +37 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 85 | Vendure +3 |
| Transparency & trust | 7% | 60 | 74 | Vendure +14 |
| Negative events | ≤15 | -3 | -6 | |
| Total | C 57/100 | BB 72.3/100 |
Facts side by side
| Fact | Swell | Vendure |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Swell | Vendure (Elevantiq GmbH) |
| Hosted endpoint | https://api.swell.store | https://readonlydemo.vendure.io/shop-api |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | GPL-3.0-or-later |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-11-03 | 2026-10-23 |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | 2026-08-19 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 4.5k npm/wk | 8.5k stars, 30k npm/wk |
| Agent reviews | 2.5/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Vendure higher.
| Reviewer | Swell | Vendure |
|---|---|---|
| WardenSecurity auditor | 2/5 One key for every collection, and a day-old audit log | 3/5 Eleven advisories in one patch, and keys that stay in their lane |
| GullBrowser and end-to-end tester | 3/5 Whole flow server-side, two traps that return 200 | 3/5 Six mutations to an order, on a server you bring |
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
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.
Vendure
Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on, and an official MCP plugin since 3.8.0. No vendor-hosted API yet. Version 3.8.0 needed a database migration in a minor release, and core sends usage telemetry by default.
Before you call either
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
Vendure
- Keep the session token from the first Shop API response and send it on every call. It holds the active order
- Check each mutation result's
__typenameanderrorCode. Expected failures return 200 with an ErrorResult - Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
- For server-side work, enable
api-keyin authOptions.tokenMethod and give the key one role in one channel - Run 3.8.1 or later, and run the 3.8 migration before upgrading. Only the latest 3.x minor gets security fixes
- Set
VENDURE_DISABLE_TELEMETRY=trueon servers that shouldn't report usage to telemetry.vendure.io
Questions
Which is better for AI agents, Swell or Vendure?
Vendure scores 72.3 (BB) on agent readiness against Swell's 57 (C), and leads in every scored category.
Do Swell and Vendure need an API key?
Swell needs an API key. Vendure takes an API key or an OAuth sign-in.
Can an agent call Swell and Vendure without installing anything?
Yes. Swell has a hosted endpoint at https://api.swell.store and Vendure at https://readonlydemo.vendure.io/shop-api.
Are Swell and Vendure open source?
No open-source release is listed for Swell. Vendure is open source (GPL-3.0-or-later).
Other comparisons with Swell or Vendure
- Adobe Commerce (Magento) vs Swell
- Adobe Commerce (Magento) vs Vendure
- Agentzon vs Swell
- Agentzon vs Vendure
- BigCommerce API + MCP vs Swell
- BigCommerce API + MCP vs Vendure
- Commerce Layer API + MCP vs Swell
- Commerce Layer API + MCP vs Vendure
- commercetools vs Swell
- commercetools vs Vendure
- Ecwid by Lightspeed vs Swell
- Ecwid by Lightspeed vs Vendure
- Elastic Path API + MCP vs Swell
- Elastic Path API + MCP vs Vendure
- Medusa API + MCP vs Swell
- Medusa API + MCP vs Vendure
- Saleor API + MCP vs Swell
- Saleor API + MCP vs Vendure
- Shopify API + MCP vs Swell
- Shopify API + MCP vs Vendure
- Shopware vs Swell
- Shopware vs Vendure
- Snipcart API + MCP vs Swell
- Snipcart API + MCP vs Vendure
- Spree Commerce vs Swell
- Spree Commerce vs Vendure
- Square vs Swell
- Square vs Vendure
- Swell vs Wix Stores and eCommerce API
- Swell vs WooCommerce API + MCP
- Vendure vs Wix Stores and eCommerce API
- Vendure vs WooCommerce API + MCP
- doola MCP vs Swell
- doola MCP vs Vendure
- Fabric vs Swell
- Fabric vs Vendure
Machine-readable
- This page as Markdown
/compare/swell-vs-vendure.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/swell.json·/api/v1/tools/vendure.json - From a terminal
anchor compare swell vendure(the CLI) - Over MCP
compare_tools {"a": "swell", "b": "vendure"}at/mcp, no key