Lemon Squeezy vs Polar for AI agents
As of 12 Oct 2026, both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human).
- Find: Some docs for agents: An MCP server.
- 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: gets in only when a person signs up and makes the key. Our agent stopped at signup, where an "I'm not a robot" checkbox sits between a business form and account creation, with no API or CLI way around it. Past that wall it reached only the public docs, the License API and the official JS SDK; calling the core endpoints without a key returned Unauthenticated, and no key, account or product work could be driven. Paying, cancelling and deleting were never reached: no account existed to test them against.
Driven 12 Oct 2026 · The drive and its evidence- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- 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 before it does anything: L1 · Needs a person. Our agent stopped at signup: email sign-in on /auth shows a Cloudflare Turnstile widget, and it answered "Verification failed. Please try again." to our agent's browser. Other routes are Google, Apple or GitHub OAuth; none lets an API or CLI create an account. Dynamic client registration works headless, but authorizing still routes through that same Turnstile sign-in, so no token, no first call, no work done. Docs are agent-ready: llms.txt, Markdown pages, OpenAPI, a CLI, an OAuth MCP server. Paying and leaving stay untested: plan switches sit behind that same human sign-in, and the API has no operation to delete an account.
Driven 12 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.
Lemon SqueezyStopped at sign up: needs a human
PolarStopped at sign up: needs a human
| Checkpoint | Lemon Squeezy | Polar |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Needs a human |
| Verify | Not reached | Not reached |
| Key | Not reached | Not reached |
| First call | Not reached | Not reached |
| First action | Not reached | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not reached |
| Delete | Not reached | Not reached |
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
| Lemon Squeezy | Polar | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (third-party) | Yes (official) |
| CLI | No | Yes |
| SDK | Yes | Yes |
| llms.txt | No | Yes |
Bot checks, and where a person was needed.
| Lemon Squeezy | Polar | |
|---|---|---|
| Bot check | reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge | Cloudflare Turnstile stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A check of our network and browser |
| First wall | reCAPTCHA checkbox on the sign-up form | Cloudflare Turnstile on the email sign-in |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. 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.
| Lemon Squeezy | Polar | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 45 of 100, poor | 100 of 100, good |
| Standards | None recorded | MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Lemon Squeezy | Polar | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Lemon Squeezy: Payment not reached.
- Polar: Payment not reached.
Lemon Squeezy vs Polar: the short answers.
Which can an AI agent use, Lemon Squeezy or Polar?
Both reach L1 · Needs a person, and with each our agent was stopped at sign up (needs a human). Both driven 12 Oct 2026.
Can an AI agent sign up for Lemon Squeezy and Polar on its own?
Lemon Squeezy: no, needs a human. Polar: no, needs a human.
Do Lemon Squeezy and Polar have an MCP server?
Lemon Squeezy: yes (third-party). Polar: yes (official).
Can an AI agent delete its Lemon Squeezy or Polar account?
Lemon Squeezy: not reached. Polar: not reached.
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.