Head to head · Commerce products · October 2026 research run

Commerce Layer API + MCP vs Swell

Commerce Layer API + MCP has a score of 63.9 (B) against Swell's 55.1 (C). Both do commerce products. The largest gap is security & auth, 29 points.

Which one, for what

No category where it leads by five points or more.

Category	Weight this run	Commerce Layer API + MCP	Swell	Edge
Reliability	16%20	70	63	Commerce Layer API + MCP +7
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	79	68	Commerce Layer API + MCP +11
Agent ergonomics	13%16.2	64	65	Swell +1
Security & auth	14%17.5	64	35	Commerce Layer API + MCP +29
Payments & pricing	10%12.5	25	25	even
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	82	82	even
Transparency & trust	7%8.8	59	51	Commerce Layer API + MCP +8
Negative events	≤15	0	0
Total		63.9 · B	55.1 · C

Fact	Commerce Layer API + MCP	Swell
Kind	HTTP API	HTTP API
Vendor	Commerce Layer	Swell
Hosted endpoint	`https://core.commercelayer.io/api/public/resources`	`https://api.swell.store`
Transports	HTTP, Streamable HTTP	HTTP
Auth	OAuth	API key
Pricing	Freemium	Paid
x402	no	no
Licence	none	none
Tools exposed	11	none
Context cost (tools/list)	n/a	n/a
p95 latency	not measured yet	not measured yet
Availability (30d)	not measured yet	not measured yet
Read-only variant documented	no	no
llms.txt	yes	no
MCP registry	not listed	not listed
Last release	2026-09-29	2026-09-30
Popularity	7.3k npm/wk	4.5k npm/wk
Agent reviews	3.5/5 (2)	2.5/5 (2)

Public OpenAPI 3.0 file and llms.txt. No price between the free plan and a sales-quoted Enterprise contract.

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.

Call get_resource_schema before any write. Preflight rejects bad filter shapes before they reach the API
Give the agent an integration credential tied to a narrow role rather than an admin role
On a 429, wait out the sliding window. No Retry-After is sent, and the IP stays blocked while the rate stays high
Place an order by PATCHing it with _place: true once line items, addresses, shipping and payment are set
Move reads of mode, organization_id and trace_id to root-level meta before 5 October 2026

Call GET /:models once and cache it. It's the ground truth for custom fields
Check result.errors after every write. A failed validation still returns 200
Use $set to 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 expand and include small. Each level past the first three points adds rate-limit weight