Front vs Gorgias for AI agents
As of 11 Oct 2026, both reach L1 · Needs a person, and our agent got as far with each: with Front it was stopped at sign up (needs a human), with Gorgias it was stopped at sign up (blocked).
- 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
L1 · Needs a person: front.com/signup requires a phone number our agent didn't have, so it stopped there. No CAPTCHA blocked it; the form itself did. Docs are strong for an agent: llms.txt, Markdown pages, an OpenAPI spec and an official MCP server. But tokens and MCP OAuth clients are only made by an admin inside an account, with no sign-up API, no DCR and no device flow. With no account, no call, no core work and no purchase were reached: Front never let our agent past the door.
Driven 6 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: 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 evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
FrontStopped at sign up: needs a human
GorgiasStopped at sign up: blocked
| Checkpoint | Front | Gorgias |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Blocked |
| 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
| Front | Gorgias | |
|---|---|---|
| Headless (checkpoints) | 1 | 1 |
| In a browser (checkpoints) | 0 | 0 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 7 | 7 |
| Work done | Not measured | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Front | Gorgias | |
|---|---|---|
| Bot check | None met | Cloudflare Turnstile (invisible) plus reCAPTCHA v3 stopped it at sign up, without a visible challenge |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | Phone number required on trial sign-up form | Invisible Turnstile on the sign-up form |
| 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.
| Front | Gorgias | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 90 of 100, good |
| Standards | OpenAPI 3.0.0 (2 versions behind) | MCP spec of 25 Nov 2025 (1 version behind) · 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.
| Front | Gorgias | |
|---|---|---|
| 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
- Front: Payment not reached.
- Gorgias: Payment not reached.
Front vs Gorgias: the short answers.
Which can an AI agent use, Front or Gorgias?
Both reach L1 · Needs a person, and our agent got as far with each: with Front it was stopped at sign up (needs a human), with Gorgias it was stopped at sign up (blocked). Driven 6 Oct 2026 (Front) and 11 Oct 2026 (Gorgias).
Can an AI agent sign up for Front and Gorgias on its own?
Front: no, needs a human. Gorgias: no, blocked.
Do Front and Gorgias have an MCP server?
Front: yes (official). Gorgias: yes (official).
Can an AI agent delete its Front or Gorgias account?
Front: not reached. Gorgias: 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.