Ecwid vs Gumroad for AI agents
As of 12 Oct 2026, Gumroad 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: Sign-up in a browser.
- Use: 10% of the work.
- Pay: No plan to buy.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 10% of the work done. Next: do half of the core work (now 10%)
Gets in on its own: L2 · Gets in. Sign-up is a web form, with no challenge, and account verification arrived by email. Getting a token needs one browser step, at Settings, Advanced, Applications; the official CLI's OAuth flow also needs a logged-in browser for the authorize click. From there our agent worked headless: calls to the REST API and the official MCP server created and read back products. Products stay drafts: publishing needs a payout method with identity verification, so no sale went through. There is no paid tier to cancel. Deleting the account, in Settings under Advanced, worked on its own, and the token stopped answering afterward.
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
GumroadIn on its own; 10% of the work done
| Checkpoint | Ecwid | Gumroad |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| Verify | Not reached | Headless |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | Not needed |
| Cancel | Not reached | Not needed |
| Delete | Not reached | In a browser |
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 | Gumroad | |
|---|---|---|
| Headless (checkpoints) | 1 | 4 |
| In a browser (checkpoints) | 0 | 3 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 0 |
| Work done | Not measured | 10% of the core |
| API | Yes | Yes |
| OpenAPI | No | No |
| MCP server | No | Yes (official) |
| CLI | No | Yes |
| SDK | No | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Ecwid | Gumroad | |
|---|---|---|
| Bot check | Cloudflare Turnstile stopped it at sign up, with a visible challenge | None met |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | Cloudflare Turnstile on the sign-up form | None |
| 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 | Gumroad | |
|---|---|---|
| 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 26 Mar 2025 (3 versions behind) · MCP discovery (behind) · MCP client registration (behind) |
| Security | No review in this drive | Reported privately to the owner |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Ecwid | Gumroad | |
|---|---|---|
| Pay | Payment not reached | No plan to buy |
| Free plan or trial | None | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Ecwid: Payment not reached.
- Gumroad: No plan to buy.
Ecwid vs Gumroad: the short answers.
Which can an AI agent use, Ecwid or Gumroad?
Gumroad 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 Gumroad it got in on its own and did 10% of the work. Driven 12 Oct 2026 (Ecwid) and 6 Oct 2026 (Gumroad).
Can an AI agent sign up for Ecwid and Gumroad on its own?
Ecwid: no, needs a human. Gumroad: yes, in a browser.
Do Ecwid and Gumroad have an MCP server?
Ecwid: none found. Gumroad: yes (official).
Can an AI agent delete its Ecwid or Gumroad account?
Ecwid: not reached. Gumroad: yes, in a browser.
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.