Ecwid vs Shopify for AI agents
As of 12 Oct 2026, Shopify gets an AI agent further: L2 · Gets in against L1 · Needs a person.
- Find: Some docs for agents: llms.txt.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Needs a person, L1, stops any agent before it reaches a key. Our agent read Ecwid's developer docs well: llms.txt, Markdown pages, a docs-search MCP. Sign-up itself ends it. The control panel form shows a visible Cloudflare Turnstile checkbox, and there is no API route to open a store. Past that wall, the docs say the REST API only works for paid-plan stores, and tokens come only from a custom app inside the control panel. A person has to carry the work the rest of the way. No plan or trial was started, so paying and cancelling were never tested; no account existed to delete.
Driven 12 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Key by API.
- Use: 33% of the work.
- Pay: Payment not reached.
- Leave: Nothing to cancel: Can't delete what it made.
Got in; payment not reached. Next: do half of the core work (now 33%)
Gets in on its own: L2 · Gets in. Through the documented no-account route, our agent ran the CLI and created a working store with no email. It then used the Admin API for products, inventory, themes, metaobytes, bundles, shipping and discounts, reading each back through GraphQL. Account sign-up stopped at a Cloudflare "Verify you are human" challenge, so orders, customers, payments and plans stayed out of reach. Our agent found no purchase path on Shopify's own domains and started no paid plan, so there was nothing to cancel. It deleted every resource it created, but the store itself could not be deleted: the CLI answered that it could not determine which organization owns it.
Gets furtherDriven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
EcwidStopped at sign up: needs a human
ShopifyGot in; payment not reached
| Checkpoint | Ecwid | Shopify |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Not needed |
| Verify | Not reached | Not needed |
| Key | Not reached | Headless |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Ecwid | Shopify | |
|---|---|---|
| Headless (checkpoints) | 1 | 4 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 7 | 1 |
| Work done | Not measured | 33% of the core |
| API | Yes | Yes |
| OpenAPI | No | No |
| MCP server | No | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Ecwid | Shopify | |
|---|---|---|
| Bot check | Cloudflare Turnstile stopped it at sign up, with a visible challenge | Cloudflare challenge on Shopify account sign-up; it got in another way |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Cloudflare Turnstile on the sign-up form | Got in; payment not reached |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| Ecwid | Shopify | |
|---|---|---|
| Level | L1 · Needs a person | L2 · Gets in |
| Agent-ready setup | 50 of 100, fair | 75 of 100, fair |
| Standards | None recorded | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Ecwid | Shopify | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | None | Trial, no card |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- Ecwid: Payment not reached.
- Shopify: Payment not reached.
Ecwid vs Shopify: the short answers.
Which can an AI agent use, Ecwid or Shopify?
Shopify gets an AI agent further: L2 · Gets in against L1 · Needs a person. With Ecwid our agent was stopped at sign up (needs a human); with Shopify it got in (payment not reached). Driven 12 Oct 2026 (Ecwid) and 6 Oct 2026 (Shopify).
Can an AI agent sign up for Ecwid and Shopify on its own?
Ecwid: no, needs a human. Shopify: not needed.
Do Ecwid and Shopify have an MCP server?
Ecwid: none found. Shopify: yes (official).
Can an AI agent delete its Ecwid or Shopify account?
Ecwid: not reached. Shopify: blocked.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.