Head to head · Commerce catalogues · October 2026 research run

BigCommerce API + MCP vs Swell

BigCommerce API + MCP scores 69.9 (B) on agent readiness against Swell's 57 (C), and leads in 4 of 7 scored categories. Swell leads on schema & documentation. Both do commerce catalogues.

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

Which one, for what

BigCommerce API + MCP B

Best for Agents working with existing BigCommerce stores, for back-office automation through REST or guest shopping through the MCP.

Ahead on

  • Reliability, 77 against 67
  • Security & auth, 70 against 42
  • Payments & pricing, 60 against 38
  • Transparency & trust, 77 against 60

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Swell loses 3 points for them

Watch for

The storefront MCP has no back-office tools and documents no tool annotations; back-office tools are only in an invite-only closed beta

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

  • Schema & documentation, 71 against 66

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 BigCommerce API + MCP +28

BigCommerce API + MCP 70

API accounts issue a token limited by OAuth scopes chosen at creation and revocable by deleting the account, but tokens never expire and can't be rotated in place (24). Read-only scope variants, and the storefront MCP has no back-office tools, so a guest agent can only shop. The invite-only Store Management MCP beta adds OAuth 2.1 with PKCE, per-scope grants that start at none, products and promotions created hidden or disabled, and refunds only after a quote, but it isn't generally available, so it moves no line (16). The MCP returns merchant product content with no prompt-injection guidance found (5). The store logs API (GET /v3/store/systemlogs) keeps storefront events such as order status changes for 365 days, and the control panel keeps staff action logs (a status incident on 8 July names them). No per-call API log found (8). Trust centre lists PCI DSS Level 1 as merchant and service provider, SOC 1, SOC 2 and SOC 3, ISO/IEC 27001:2022 with 27017, 27018 and 27701, and a vulnerability disclosure programme run through Inspectiv. No security.txt (404 on 2 November) (17).

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.

Payments & pricing BigCommerce API + MCP +22

BigCommerce API + MCP 60

No x402, MPP or L402 (0). Plan prices public, Core $39, Growth $105 and Scale $399 a month with GMV caps and 2.0, 1.0 and 0.6 per cent on orders through non-embedded providers, but nothing per call (10). 15-day free trial, and the pricing page says no credit card is needed (20). An agent can shop any store that has switched on the MCP as a guest with no key, but back-office access needs a person to create an API account (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.

Transparency & trust BigCommerce API + MCP +17

BigCommerce API + MCP 77

Closed platform with published terms, now on commerce.com, and an open-source Catalyst storefront (15). The trust centre lists a DPA and a subprocessor document. The commerce.com privacy policy wasn't read in either pass (22). A Deprecations and Sunsets page lists deprecated v2 endpoints and three dated sunsets, the last on 3 June 2024, but the current deprecations carry no sunset dates and no notice period is stated (10). Subprocessor document listed and Google Cloud named as the host (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 BigCommerce API + MCP +10

BigCommerce API + MCP 77

Atlassian Statuspage at status.bigcommerce.com with API & Webhooks, Checkout & Payment Processing, Storefront and B2B components, a history page and an Atom feed (20). Read on 2 November, the history holds 36 incidents from 4 August, 8 in August, 8 in September and 20 in October. Seven carry a major or critical label, each partial by its own text. Microsoft single sign-on failed for a subset of stores for 29 minutes (25 August), Modern Import/Export catalogue export failed for 65 minutes (14 September), the Contact Center phone system was down (16 September, not the platform), category pages showed inaccurate stock (23 September), QuickBooks Payments stores couldn't take payments for 3 hours 39 minutes (5 October, one provider), some Chrome on Android shoppers on headless storefronts couldn't reach checkout (26 October), and Bolt payments failed for 2 hours 12 minutes after Bolt changed its domain (27 October, one provider). Search returned HTTP 500s across the platform for 66 minutes on 27 October, search only, and Management API add-to-cart requests failed for 59 minutes on 12 October. The 10 July availability major left the window on 8 October, so with only partial incidents the line is 20 (was 10, cause time). Published limits, 450 requests per 30 seconds on Scale and 150 on Growth and Core, refreshed every 30 seconds (15). A 429 carries X-Rate-Limit-Time-Reset-Ms and the docs advise waiting that long, then backing off exponentially. No idempotency keys for writes found (12). No SLA found (0). REST APIs are generally available, and the storefront MCP pages no longer carry a beta label, with the server switched on from the standard Settings, API and MCP page. The invite-only Store Management MCP beta isn't graded (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.

Schema & documentation Swell +5

BigCommerce API + MCP 66

Reference pages are built from API specs (a 29 September changelog entry corrected twenty of them), but the public spec repo was archived in December 2023 and its successor, bigcommerce/docs, still asked git for credentials on 2 October, so no current spec file was found (10). llms.txt hub linking a developer index of about 500 Markdown pages, plus a docs MCP server (10). Reference descriptions say what each call does, and the MCP tools are guest shopping steps (12). Typed REST parameters in the reference (11). Examples in the reference, but the developer index has no page on error responses (10). Dated changelog with entries almost daily, v2 and v3 REST paths, and a Deprecations and Sunsets page, though it gives no notice period (13).

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.

Score by category

CategoryWeightBigCommerce API + MCPSwellEdge
Reliability16%7767BigCommerce API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6671Swell +5
Agent ergonomics13%6265Swell +3
Security & auth14%7042BigCommerce API + MCP +28
Payments & pricing10%6038BigCommerce API + MCP +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8282even
Transparency & trust7%7760BigCommerce API + MCP +17
Negative events≤150-3
TotalB 69.9/100C 57/100

Facts side by side

FactBigCommerce API + MCPSwell
KindHTTP APIHTTP API
VendorBigCommerce (Commerce.com)Swell
Hosted endpointhttps://api.bigcommerce.comhttps://api.swell.store
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
Tools exposed7none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-11-03
Terms last updated2026-06-01no date given
Privacy policy last updated2026-01-282026-08-19
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone4.5k npm/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates BigCommerce API + MCP 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

BigCommerce API + MCP

Rate limits are published per plan, and every 429 carries X-Rate-Limit-Time-Reset-Ms. Status incidents since August were partial. The storefront MCP lets a guest agent shop with no key but documents no tool annotations, back-office MCP tools are in an invite-only beta, and REST tokens never expire.

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

BigCommerce API + MCP

  1. Give the agent a store-level API account with only the scopes the task needs, and delete it when done
  2. On a 429, wait X-Rate-Limit-Time-Reset-Ms before retrying
  3. Expect up to 10 minutes after a store owner enables the MCP before the URL answers
  4. The MCP stops at a checkout URL. Payment happens in the shopper's browser
  5. Point a coding agent at the docs MCP at https://docs.bigcommerce.com/_mcp/server
  6. Store Management MCP is invite-only; if granted, call get_refund_quote and confirm with a person before create_refund, which the docs say is never safe to retry

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, BigCommerce API + MCP or Swell?

BigCommerce API + MCP scores 69.9 (B) on agent readiness against Swell's 57 (C), and leads in 4 of 7 scored categories. Swell leads on schema & documentation.

Do BigCommerce API + MCP and Swell need an API key?

BigCommerce API + MCP takes an API key or an OAuth sign-in. Swell needs an API key.

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

Yes. BigCommerce API + MCP has a hosted endpoint at https://api.bigcommerce.com and Swell at https://api.swell.store.

Other comparisons with BigCommerce 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.