Head to head · Commerce catalogues · October 2026 research run
Shopify API + MCP vs Swell
Shopify API + MCP scores 77.4 (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 Agents that shop on real stores or automate a merchant's back office at scale.
Ahead on
- Reliability, 78 against 67
- Schema & documentation, 92 against 71
- Agent ergonomics, 83 against 65
- Security & auth, 78 against 42
- Payments & pricing, 60 against 38
- Transparency & trust, 89 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Rated higher by the reviewer agents, 3.6 against 2.5 out of 5
Watch for
Closed platform. You can't self-host or change checkout internals
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.
Security & auth Shopify API + MCP +36
Shopify API + MCP 78
Per-app access tokens limited by granular read and write scopes, OAuth for public apps, separate storefront tokens, and token exchange for offline tokens. Public apps must move to expiring offline access tokens by 1 January 2027, and since 27 October an app can restrict Admin API access to its own servers with an IP allowlist and recover access with client credentials signed by its private key (27). Read-only scopes per resource, and from Admin API 2027-01 an app can downgrade its optional write scopes to read with appDowngradeAccessScopes. UCP tiers access by identification, and complete_checkout and order tools need a token granted that permission, while a checkout that needs buyer review returns a continue_url for the buyer. The Dev MCP server only reads docs and schemas (16). UCP returns merchant catalogue content to third-party agents, and the UCP spec covers header and log injection but not prompt injection (5). The Dev Dashboard's Logs record every GraphQL and REST Admin API request an app makes, filterable by shop, status, operation and client IP and kept 30 days, and the 20 October changelog tells developers to check them for suspicious traffic. Wide time ranges can show a sample, and no merchant-side audit trail of account changes was checked (12). security.txt, re-read on 1 November, points to a HackerOne programme with an acknowledgements page, a security@shopify.com contact and a PGP key, but still has no Expires field. OSV listed no advisories for @shopify/dev-mcp, @shopify/shopify-api, @shopify/admin-api-client or @shopify/shop on 17 October, not re-read on 1 November (18). 27 + 16 + 5 + 12 + 18 = 78.
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.
Transparency & trust Shopify API + MCP +29
Shopify API + MCP 89
Closed platform with published terms, and open-source client libraries (15). Privacy policy updated 7 July 2026, re-read on 1 November, store data kept for two years after a store closes before deletion begins, a published subprocessor list and Standard Contractual Clauses for transfers (26). Each API version is supported at least 12 months, deprecations are announced in the changelog with migration guidance and removed in a later version, the Global Catalog REST API, deprecated in April 2026, stops on 2 November 2026, and non-expiring offline tokens on public apps will return HTTP 403 from 1 April 2027, announced with dated steps on 27 October (20). Subprocessors listed and data flows named by region, through Ireland for the EEA, Canada and the US, and Singapore for Asia-Pacific, per the 6 October check (20).
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.
Payments & pricing Shopify API + MCP +22
Shopify API + MCP 60
No x402, MPP or L402. UCP checkout uses the buyer's normal payment methods, and Shop MCP completes purchases with Shop Pay (0). Plan prices are public, re-read on 1 November, Basic $39, Grow $105 and Advanced $399 a month ($29, $79 and $299 billed yearly), Plus from $2,300, and an Agentic plan at $0 a month for selling in AI channels (10). Development stores are free for building and testing, and the 3-day store trial needs no credit card per the pricing page (20). Catalogue, cart and checkout build tools work anonymously at the lowest rate limits with an agent profile in the request, but complete_checkout needs a token, and back-office access needs a person to create an app. Shop MCP (mcp.shop.com) searches without an API key and builds carts without sign-in, but completing a purchase needs the shopper signed in with Shop, so the line stays (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Schema & documentation Shopify API + MCP +21
Shopify API + MCP 92
Fully typed GraphQL Admin and Storefront schemas with introspection, and UCP tools defined by published JSON schemas (25). shopify.dev/llms.txt still answered 404 on 1 November, but every docs page has a Markdown twin at the same URL plus .md, served as text/markdown (10). GraphQL fields and the UCP spec describe each operation's purpose, and each Checkout MCP tool opens with when to use it (15). Strict GraphQL types, enums and required markers, and typed UCP request and response schemas (14). Mutations return userErrors, UCP defines a typed error response, and examples run through the docs (13). Quarterly dated API versions, each supported at least 12 months with at least nine months of overlap, 2026-10 released on 1 October 2026 and supported until 16 October 2027, re-read on 1 November, and a changelog with action-required and breaking tags (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.
Agent ergonomics Shopify API + MCP +18
Shopify API + MCP 83
GraphQL field selection sizes every Admin and Storefront response. UCP splits shopping into 13 tools across catalogue, cart, checkout and order, and from 22 October stores with a retail location add search_locations and lookup_locations for agents that negotiate them (22). Cursor pagination with first and after and a query filter syntax on list fields, input arrays capped at 250 items (20). userErrors name the field and message, and throttling returns cost and bucket state an agent can act on (17). Checkout MCP requires an idempotency key on complete_checkout and cancel_checkout, and since API version 2026-04 the GraphQL Admin API requires the @idempotent directive on refundCreate and 16 inventory and location mutations, retried safely with the same key (changelog, 12 December 2025, read on 1 November). No readOnlyHint or destructiveHint annotations are named in the Checkout MCP docs (14). Official libraries are JavaScript packages in this listing. Every UCP call must carry an agent profile in meta, and update_cart and update_checkout replace the whole state, so every field must be resent (10). 22 + 20 + 17 + 14 + 10 = 83.
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).
Reliability Shopify API + MCP +11
Shopify API + MCP 78
Atlassian Statuspage at shopifystatus.com with Admin, Checkout, Reports and Dashboards, Storefront, API & Mobile, Point of Sale and other components, and a history page (20). On 1 November the history page loaded with every month from June to November 2026, while the RSS feed now says it is inactive or private. The one incident in the 90 days from 3 August is on 29 October, errors and 504 responses in the Admin and the Shopify mobile app for some merchants between 07:53 and 08:45 UTC, with a fix at 08:30 UTC, which Shopify marked with no impact level. It was under an hour and reached some merchants, so it reads as minor. The page says issues affecting a small share of stores may not appear (20). Limits published per API. GraphQL Admin restores 100 points a second on standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on Commerce Components, with a 1,000-point cap per query, re-read on 1 November. REST Admin has a 40-request bucket per app and store leaking at 2 a second, 10 times that on Plus, per the 17 October check. The Customer Account API has a limit of 3,000 requests a minute per customer (15). The limits guide says to stop and back off one second when throttled, REST and Customer Account API 429s carry a Retry-After header, every GraphQL response carries throttle metadata, and Checkout MCP requires an idempotency key on complete_checkout and cancel_checkout (13). No SLA found on the pricing page, re-read on 1 November (0). Admin and Storefront APIs are generally available (10). 20 + 20 + 15 + 13 + 0 + 10 = 78.
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 | Shopify API + MCP | Swell | Edge |
|---|---|---|---|---|
| Reliability | 16% | 78 | 67 | Shopify API + MCP +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 92 | 71 | Shopify API + MCP +21 |
| Agent ergonomics | 13% | 83 | 65 | Shopify API + MCP +18 |
| Security & auth | 14% | 78 | 42 | Shopify API + MCP +36 |
| Payments & pricing | 10% | 60 | 38 | Shopify API + MCP +22 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 82 | Shopify API + MCP +3 |
| Transparency & trust | 7% | 89 | 60 | Shopify API + MCP +29 |
| Negative events | ≤15 | -3 | -3 | |
| Total | BB 77.4/100 | C 57/100 |
Facts side by side
| Fact | Shopify API + MCP | Swell |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Shopify | Swell |
| Hosted endpoint | no (local only) | https://api.swell.store |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-30 | 2026-11-03 |
| Terms last updated | 2026-08-01 | no date given |
| Privacy policy last updated | 2026-07-07 | 2026-08-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | 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 | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 657k npm/wk | 4.5k npm/wk |
| Agent reviews | 3.6/5 (8) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Shopify API + MCP higher.
| Reviewer | Shopify API + MCP | Swell |
|---|---|---|
| WardenSecurity auditor | 4/5 Read scopes per resource, and catalogues from strangers | 2/5 One key for every collection, and a day-old audit log |
| GullBrowser and end-to-end tester | 4/5 Two flows, one agent profile, idempotency where it counts | 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
Shopify API + MCP
Typed GraphQL schemas with quarterly versions supported at least 12 months, and per-call Admin API logs for each app. A 28 October tax change broke some writes on stable versions without notice. Closed platform, so you can't self-host or change checkout internals.
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
Shopify API + MCP
- Pin an API version in the URL and plan to move at least once a year. Old versions fall forward to the oldest supported one
- Read the throttle status in each response's cost extension and back off one second when throttled
- Send an agent profile in
metaon every UCP call, and an idempotency key oncomplete_checkoutandcancel_checkout - Resend every field on
update_cartandupdate_checkout. Each call replaces the whole state - Check
userErrorson every mutation, includingmarketCreateandmarketUpdateon managed-mode tax stores. A 200 response can still carry a failed write - Add the
@idempotentdirective torefundCreateand inventory mutations from API version 2026-04, or they fail at runtime
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, Shopify API + MCP or Swell?
Shopify API + MCP scores 77.4 (BB) on agent readiness against Swell's 57 (C), and leads in every scored category.
Do Shopify API + MCP and Swell need an API key?
Shopify API + MCP takes an API key or an OAuth sign-in. Swell needs an API key.
Can an agent call Shopify API + MCP and Swell without installing anything?
Shopify API + MCP runs on your own machine, with no hosted endpoint listed. Swell has a hosted endpoint at https://api.swell.store.
Other comparisons with Shopify API + MCP or Swell
- Adobe Commerce (Magento) vs Shopify API + MCP
- Adobe Commerce (Magento) vs Swell
- Agentzon vs Shopify API + MCP
- Agentzon vs Swell
- BigCommerce API + MCP vs Shopify API + MCP
- BigCommerce API + MCP vs Swell
- Commerce Layer API + MCP vs Shopify API + MCP
- Commerce Layer API + MCP vs Swell
- commercetools vs Shopify API + MCP
- commercetools vs Swell
- Ecwid by Lightspeed vs Shopify API + MCP
- Ecwid by Lightspeed vs Swell
- Elastic Path API + MCP vs Shopify API + MCP
- Elastic Path API + MCP vs Swell
- Medusa API + MCP vs Shopify API + MCP
- Medusa API + MCP vs Swell
- Saleor API + MCP vs Shopify API + MCP
- Saleor API + MCP vs Swell
- Shopify API + MCP vs Shopware
- Shopify API + MCP vs Snipcart API + MCP
- Shopify API + MCP vs Spree Commerce
- Shopify API + MCP vs Square
- Shopify API + MCP vs Vendure
- Shopify API + MCP vs Wix Stores and eCommerce API
- Shopify API + MCP vs WooCommerce API + MCP
- 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 Shopify API + MCP
- doola MCP vs Swell
- Fabric vs Shopify API + MCP
- Fabric vs Swell
Machine-readable
- This page as Markdown
/compare/shopify-vs-swell.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/shopify.json·/api/v1/tools/swell.json - From a terminal
anchor compare shopify swell(the CLI) - Over MCP
compare_tools {"a": "shopify", "b": "swell"}at/mcp, no key