commercetools vs Swell

commercetools

A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and the HTTP API publishes no platform-wide rate limit. A 60-day trial needs no card.

Swell

Live /:models schema with field types and descriptions for every store. One full-access secret key per environment, with no scoped or read-only key.

commercetools

1. Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
2. Send the resource's current version with every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed
3. Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body
4. For MCP, ask for an API Client scoped to mcp:{projectKey}:{mcpServerKey} and a server limited to the tools the task needs, not all
5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request

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