Gorgias vs Plain for AI agents
As of 11 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Gorgias it was stopped at sign up (blocked), with Plain it was stopped at sign up (needs a human).
- 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: blocked. Next: let an agent sign up on its own
L1 · Needs a person describes Gorgias today: an agent can reach the sign-up form but can't get past it alone. It stopped at signup, where an invisible Cloudflare Turnstile paired with reCAPTCHA v3 never cleared and left "Create my account" disabled. Our agent never reached verification, a key or a first call, so no work was attempted. Once a person finishes signup and hands over credentials, the surface is ready: an official MCP server with OAuth metadata and markdown API docs with OpenAPI reference. The trial needs no card, but checkout and cancellation sit inside the account our agent never opened, so neither was tested.
Driven 11 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt 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
Docs answer our agent on their own: llms.txt, markdown pages, a public GraphQL schema, SDK, CLI and an official OAuth MCP server. Sign-up does not. L1 · Needs a person: our agent gets in on its own nowhere. It stopped at signup, where a visible Cloudflare Turnstile challenge sits on the page. The email sign-in path answered "Access blocked, please contact support." With no human to hand over a workspace, no key, call or action followed. Core-api returned Unauthorized with no credentials. Paying and leaving are graded from docs only: a trial without a card and plan changes by API, since no account ever started.
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.
GorgiasStopped at sign up: blocked
PlainStopped at sign up: needs a human
| Checkpoint | Gorgias | Plain |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Blocked | 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
| Gorgias | Plain | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Gorgias | Plain | |
|---|---|---|
| Bot check | Cloudflare Turnstile (invisible) plus reCAPTCHA v3 stopped it at sign up, without a visible challenge | Cloudflare Turnstile (managed challenge) stopped it at sign up, with a visible challenge |
| Wall type | A check of our network and browser | A check of our network and browser |
| First wall | Invisible Turnstile on the sign-up form | Cloudflare Turnstile on the sign-up page |
| 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.
| Gorgias | Plain | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 75 of 100, fair |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | MCP client registration (current) |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Gorgias | Plain | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Trial, no card |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Gorgias: Payment not reached.
- Plain: Payment not reached.
Gorgias vs Plain: the short answers.
Which can an AI agent use, Gorgias or Plain?
Both reach L1 · Needs a person, and our agent got as far with each: with Gorgias it was stopped at sign up (blocked), with Plain it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Gorgias) and 6 Oct 2026 (Plain).
Can an AI agent sign up for Gorgias and Plain on its own?
Gorgias: no, blocked. Plain: no, needs a human.
Do Gorgias and Plain have an MCP server?
Gorgias: yes (official). Plain: yes (official).
Can an AI agent delete its Gorgias or Plain account?
Gorgias: not reached. Plain: 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.