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).

FrontL1Needs a person
  • 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
GorgiasL1Needs a person
  • 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

The 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

Front and Gorgias, checkpoint by checkpoint
CheckpointFrontGorgias
DocsHeadlessHeadless
Sign upNeeds a humanBlocked
VerifyNot reachedNot reached
KeyNot reachedNot reached
First callNot reachedNot reached
First actionNot reachedNot reached
PayNot reachedNot reached
CancelNot reachedNot reached
DeleteNot reachedNot 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
Checkpoints by how our agent passed them, and what each product offers an agent
FrontGorgias
Headless (checkpoints)11
In a browser (checkpoints)00
Needs a human (checkpoints)10
Blocked (checkpoints)01
Not tested (checkpoints)77
Work doneNot measuredNot measured
APIYesYes
OpenAPIYesYes
MCP serverYes (official)Yes (official)
CLINoNo
SDKNoNo
llms.txtYesYes

Bot checks, and where a person was needed.

Walls our agent met
FrontGorgias
Bot checkNone metCloudflare Turnstile (invisible) plus reCAPTCHA v3 stopped it at sign up, without a visible challenge
Wall typeNo bot-check wallA check of our network and browser
First wallPhone number required on trial sign-up formInvisible Turnstile on the sign-up form
A person helpedNoNo

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 and Gorgias: level and part scores, 0 to 100
FrontGorgias
LevelL1 · Needs a personL1 · Needs a person
Agent-ready setup90 of 100, good90 of 100, good
StandardsOpenAPI 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.

Paying, cancelling and deleting the account
FrontGorgias
PayPayment not reachedPayment not reached
Free plan or trialTrial, no cardTrial, no card
CancelNot reachedNot reached
Delete the accountNot reachedNot 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.