Gumroad vs Shopify for AI agents
As of 6 Oct 2026, both reach L2 · Gets in. Our agent got further with Gumroad: with Gumroad it got in on its own and did 10% of the work, with Shopify it got in (payment not reached).
- 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 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.
Driven 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.
GumroadIn on its own; 10% of the work done
ShopifyGot in; payment not reached
| Checkpoint | Gumroad | Shopify |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Not needed |
| Verify | Headless | Not needed |
| Key | In a browser | Headless |
| First call | Headless | Headless |
| First action | Headless | Headless |
| Pay | Not needed | Not reached |
| Cancel | Not needed | Not needed |
| Delete | In a browser | 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
| Gumroad | Shopify | |
|---|---|---|
| Headless (checkpoints) | 4 | 4 |
| In a browser (checkpoints) | 3 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 1 |
| Work done | 10% of the core | 33% of the core |
| API | Yes | Yes |
| OpenAPI | No | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Gumroad | Shopify | |
|---|---|---|
| Bot check | None met | Cloudflare challenge on Shopify account sign-up; it got in another way |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | None | 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.
| Gumroad | Shopify | |
|---|---|---|
| Level | L2 · Gets in | L2 · Gets in |
| Agent-ready setup | 75 of 100, fair | 75 of 100, fair |
| Standards | MCP spec of 26 Mar 2025 (3 versions behind) · MCP discovery (behind) · MCP client registration (behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) |
| Security | Reported privately to the owner | No review in this drive |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Gumroad | Shopify | |
|---|---|---|
| Pay | No plan to buy | Payment not reached |
| Free plan or trial | Free plan | Trial, no card |
| Cancel | Not needed | Not needed |
| Delete the account | In a browser | Blocked |
How each one takes payment
- Gumroad: No plan to buy.
- Shopify: Payment not reached.
Gumroad vs Shopify: the short answers.
Which can an AI agent use, Gumroad or Shopify?
Both reach L2 · Gets in. Our agent got further with Gumroad: with Gumroad it got in on its own and did 10% of the work, with Shopify it got in (payment not reached). Both driven 6 Oct 2026.
Can an AI agent sign up for Gumroad and Shopify on its own?
Gumroad: yes, in a browser. Shopify: not needed.
Do Gumroad and Shopify have an MCP server?
Gumroad: yes (official). Shopify: yes (official).
Can an AI agent delete its Gumroad or Shopify account?
Gumroad: yes, in a browser. 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.