Gorgias vs tawk.to 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 tawk.to 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
Stopped at sign-up: L1 · Needs a person. Our agent read tawk.to's docs fine: llms.txt, the developer portal and the help center. The only sign-up route is a web form, and a Cloudflare Turnstile check stopped it there with "Human verification failed." No account followed. The key, the first call and real work stayed out of reach. Even a human's REST API key needs a separate approved access request first. Paying and cancelling live in the dashboard, by card or PayPal, with no billing API. Our agent never got far enough to see checkout.
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
tawk.toStopped at sign up: needs a human
| Checkpoint | Gorgias | tawk.to |
|---|---|---|
| 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 | tawk.to | |
|---|---|---|
| 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 (third-party) |
| CLI | No | No |
| SDK | No | No |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Gorgias | tawk.to | |
|---|---|---|
| Bot check | Cloudflare Turnstile (invisible) plus reCAPTCHA v3 stopped it at sign up, without a visible challenge | Cloudflare Turnstile 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 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.
| Gorgias | tawk.to | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Agent-ready setup | 90 of 100, good | 55 of 100, fair |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP client registration (behind) · OpenAPI 3.1.0 (1 version behind) | None recorded |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Gorgias | tawk.to | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Trial, no card | Free plan |
| Cancel | Not reached | Not reached |
| Delete the account | Not reached | Not reached |
How each one takes payment
- Gorgias: Payment not reached.
- tawk.to: Payment not reached.
Gorgias vs tawk.to: the short answers.
Which can an AI agent use, Gorgias or tawk.to?
Both reach L1 · Needs a person, and our agent got as far with each: with Gorgias it was stopped at sign up (blocked), with tawk.to it was stopped at sign up (needs a human). Driven 11 Oct 2026 (Gorgias) and 6 Oct 2026 (tawk.to).
Can an AI agent sign up for Gorgias and tawk.to on its own?
Gorgias: no, blocked. tawk.to: no, needs a human.
Do Gorgias and tawk.to have an MCP server?
Gorgias: yes (official). tawk.to: yes (third-party).
Can an AI agent delete its Gorgias or tawk.to account?
Gorgias: not reached. tawk.to: 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.