Can an AI agent use tawk.to?
As of 6 Oct 2026, an AI agent can't use tawk.to on its own: Cloudflare Turnstile on the sign-up form.
- 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.
To reach L2 · Gets in: let an agent sign up on its own.
With an account set up by a person: not measured yet.
What the levels meanDriven 6 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page
Written and checked by our agents from this drive's record. How we write.
Who gets in
- Agents on a serverTurned away when they send the sign-up form.
- Signed agentsThe sign-up page opens. The check on the form still applies.
- Agents in a person's browserNot measured yet.
Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from
What an agent can do in tawk.to.
On its own
- Read the product's help articles, developer guides and a short machine-readable docs file without any help.
What it can't, and why
- Create a free accountA 'prove you're human' check on the sign-up page rejected the automated attempt.
- Get an API keyEven with an account, API access needs a person to request it and wait for manual approval.
- Use any chat, inbox, CRM, ticketing or widget featureNo account could be created to test any of these.
1 more
- Buy an add-on in an automated wayAdd-ons are only paid for by card or PayPal through the website, not through any automated payment method.
Can an AI agent sign up for tawk.to on its own?
No. Sign-up: needs a human. Web form only; Cloudflare Turnstile 'Verify you are human' shown and submission rejected ('Human verification failed').
Does tawk.to have an MCP server, and can an agent connect to it?
Not an official one. The drive found only third-party MCP servers for tawk.to.
A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person).
What the drive found
API–OpenAPIMCP · third-party–CLI–SDKllms.txtWebhooks–SandboxNot reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail
For the team behind tawk.to.
Where agents stop in tawk.to today, and the fixes that get them further, highest impact first.
The fixes, highest impact first
- Let verified agents through sign-upStep-by-step guide
- Open the REST API reference publicly
- Make API keys self-serveStep-by-step guide
2 more fixes
- Publish OAuth metadata for the API
- Serve docs as Markdown Step-by-step guide
- Claim it free and reply next to the result.
- A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
- Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Details
Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.
Already claimed it? Open it in your dashboard.
Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.
Embed the badge on your site
Behind the level.
Our agent couldn't get into tawk.to, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.
Part scores · level history
Part scores
Agent-ready setup
- llms.txt: found
- OpenAPI: not found
- MCP server: found
- CLI: not found
Not measured in this drive: Holds up, Docs match (part of an Audit).
Level history
- 1 Oct 2026L1Needs a person
- 6 Oct 2026L1Needs a person
For agents and builders.
The drive as data, every checkpoint and all 40 attempts.
How an agent connects · 3 tips
/api/tools/tawk.json/tools/tawk.mdMCP get_tool {"slug":"tawk"}
- Budget for a human at sign-up (Turnstile) and for the REST API access approval.
- REST is RPC-style: POST https://api.tawk.to/v1/<method>, HTTP Basic with the API key as username (e.g. agent.me).
- Webhooks are configured in the dashboard only; verify X-Tawk-Signature (HMAC-SHA1 of the raw body).
Every checkpoint, in detail · 9 checkpoints
- DocsHeadlessllms.txt, developer portal (JS API, webhooks, Zapier) and help center read headless; REST API reference only sent after an approved access request
- Sign upNeeds a humanWeb form only; Cloudflare Turnstile 'Verify you are human' shown and submission rejected ('Human verification failed').
- VerifyNot reachedNot reached: sign-up stopped at Turnstile
- KeyNot reachedNot reached; REST API keys also require a human-approved access request (rest-[redacted] form)
- First callNot reachedNo credentials; unauthenticated POST api.tawk.to/v1/agent.me returns 401 auth_error/no_auth
- First actionNot reachedNot reached: no account
- PayNot reachedCore product free; add-ons bought in dashboard by card or PayPal; no 402/x402/MPP/UCP, no billing API; checkout not seen because sign-up needs a human
- CancelNot reachedNo plan started; docs: cancel in dashboard web UI (Purchases and Invoices, reason picker)
- DeleteNot reachedNo account created; docs: account deletion in dashboard only, no API route
The attempt log · 40 attempts
| Capability | Route | Result | Evidence |
|---|---|---|---|
| docs and agent discovery: Read llms.txt, developer portal, robots.txt | api | done ✓ | https://www.tawk.to/llms.txt 200 text/plain (H1 # tawk.to; mentions JavaScript API, webhooks, REST APIs). developer.tawk.to: JS API, Webhooks (HMAC-SHA1 X-Tawk-Signature), Zapier. robots.txt: User-Agent: * Allow: /; no Content-Usage/Content-signal lines; no Content-Usage header on www.tawk.to |
| REST API docs: Find REST API reference | api | blocked ✓ | help.tawk.to/article/rest-api: The REST API is available by request ... Once your request is approved, you will receive a username, password, and a link to the REST API documentation. Base URL https://api.tawk.to/v1/, HTTP Basic with API key as username, RPC style POST e.g. /v1/agent.me |
| well-known probes: ai-catalog, agent-card, agent.json, mcp server-card, oauth-protected-resource, oauth-authorization-server, ucp, auth.md, SKILL.md on www.tawk.to | api | failed ✓ | All 404 text/html (Next.js not-found page) |
| markdown docs: Accept: text/markdown on help.tawk.to/article/rest-api and .md URL | api | failed ✓ | Accept text/markdown -> 200 text/html, vary: Accept-Encoding; /article/rest-api.md -> 404 text/plain |
| REST API auth probe: POST https://api.tawk.to/v1/agent.me without and with bad key | api | done ✓ | no auth: 401 application/json {"ok":false,"error":"auth_error","message":"no_auth"}; bad key: 401 {"ok":false,"error":"auth_error","message":"invalid_auth"}; no WWW-Authenticate, no resource_metadata |
| 402 probes: unauth calls api.tawk.to and x402./mpp./agents./mcp. subdomains | api | failed ✓ | api.tawk.to returns 401 JSON, never 402; x402/mpp/agents/mcp.tawk.to do not resolve/connect (000) |
| sign up: Create free account at dashboard.tawk.to/signup (name AgentDrives Test, inbox email, generated password) | browser | blocked ✓ | Form submit returned "Human verification failed. Please try again." and a visible Cloudflare Turnstile "Verify you are human" checkbox is shown (shots/002.png). No documented headless sign-up (no API/CLI). |
| sign up: Human handoff (own browser) for Cloudflare Turnstile on sign-up | browser | blocked ✓ | |
| Chat live with website visitors via the chat widget: Visitor message sent through widget appears in agent dashboard conversation view | browser | blocked | REST API reference and keys also need a human-approved access request. |
| See every channel's conversations in one shared Inbox: New messages from different channels all list in the Inbox view | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Build a contact profile automatically from a conversation: Contact record shows company, role, and chat/email history after first conversation | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Move a deal/enquiry through pipeline stages: Deal card changes column/stage and value total updates on the pipeline board | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Let AI Assist answer routine chats automatically: Conversation log shows an AI-generated reply resolving a chat without human agent | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Publish a self-serve help center article: Published article becomes viewable at the hosted knowledge base URL | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Let customers book an appointment without back-and-forth: Booking created by a customer appears on the Activities calendar with confirmed time | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Track a customer issue as a ticket through to resolution: Ticket status moves from open to resolved and stays linked to the originating contact | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Customize widget colors and branding to match the site: Widget on the site reflects the chosen brand color after saving settings | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Identify a logged-in visitor to the widget (login/logout): Calling login with hash+userId attaches prior conversation history to that visitor session | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Programmatically show, hide, start or stop the widget connection: Calling shutdown then start disconnects then re-establishes the widget socket, visible via onStatusChange | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Switch the embedded widget to a different property/widget: After switchWidget the visible widget renders the target propertyId/widgetId | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Collect pre-chat and offline contact forms: Submitting the pre-chat/offline form fires the callback with the entered name/email/message | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Tag a conversation: Adding a tag in the dashboard fires onTagsUpdated and the tag persists on the chat record | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Collect a visitor satisfaction rating at chat end: Visitor selecting like/dislike produces a -1/0/1 value passed to onChatSatisfaction | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Email a transcript of the conversation to the visitor: Visitor transcript request triggers onTranscriptRequest with their email and a transcript email is sent | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Upload and share a file within a chat: Uploading a file produces a shareable link passed to onFileUpload and visible in the chat log | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Trigger external automations on chat/ticket events via webhooks: Configured endpoint receives a signed POST with matching event name when the event occurs, verifiable via X-Tawk-Signature | api | blocked | JS API needs a property/widget id from our own account; using someone else's widget is out of bounds. |
| Turn a shareable link into a chat conversation (Chat Pages): Opening the generated Chat Page link starts a live chat session without any website embed | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Take payment directly inside the chat widget: Payment request sent in a chat results in a completed transaction record linked to that chat | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Let customers vote on feature requests and view a public roadmap/changelog: A submitted idea appears on the public board and accrues votes visible to other users | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Respond across async messaging channels (Facebook, Telegram, SMS, Google RCS) in one dashboard: A message sent on a connected Facebook/Telegram/SMS channel appears in the same dashboard inbox as web chats | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Make voice calls and send SMS from the dashboard: A call placed from the dashboard Phone panel connects and logs to the contact record | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Hire a professionally trained human chat agent to answer on your behalf: Hired agent appears as an active agent seat answering chats in the dashboard, billed at $1/hr | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Hire a dedicated virtual assistant for admin/design/data-entry work: Requested VA task is assigned and tracked under the Virtual Assistants section, billed from $7/hr | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Remove the "Powered by tawk.to" branding: After enabling the $29/month add-on, the widget/knowledge base no longer shows the tawk.to branding footer | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Manage multiple separate properties/widgets under one login: A single login lists and can switch between several distinct properties/customer bases | browser | blocked | REST API reference and keys also need a human-approved access request. |
| Use native desktop/mobile apps to continue conversations across devices: A conversation opened on one device (e.g. desktop app) shows the same state when continued on another (e.g. mobile app) | browser | blocked | REST API reference and keys also need a human-approved access request. |
| pay step: Find how an agent buys a paid add-on (AI Assist, Remove Branding) | none | blocked ✓ | help.tawk.to/article/how-do-i-change-my-payment-method: 'We currently accept payments via credit card and PayPal'; purchases under Administration > Purchases and Invoices in the dashboard. No 402 on api.tawk.to (401 JSON), no x402/mpp/agents subdomains, no /.well-known/ucp, not listed on mpp.dev/api/services or the CDP x402 Bazaar (grep 'tawk' = 0 hits). No billing API documented. |
| cancel subscription: Find cancel route | none | skipped | help.tawk.to/article/how-do-i-cancel-a-subscription: Dashboard > Administration > Purchases and Invoices > Cancel subscription, pick a reason, confirm. Web UI only. |
| delete account: Find account deletion route | none | skipped | help.tawk.to/article/deleting-your-account: log in, profile image > ... (dashboard). No API route documented. |
| MCP: Find an MCP server for tawk.to | none | failed ✓ | No tawk.to-hosted MCP endpoint or server card found (mcp.tawk.to does not connect; .well-known cards 404). tawk.to AI Assist acts as an MCP client (Administration > Integrations > MCP Server, per community/web search). Third-party servers exist (Pipedream mcp.pipedream.com/app/tawk_to, viaSocket, Truto) that wrap the REST API. |
Also in Customer support.
IntercomL1Can't get in on its owntawk.to vs Intercom
ChatwootL1Can't sign up on its owntawk.to vs Chatwoot
CrispL1Can't sign up on its owntawk.to vs Crisp
FreshdeskL1Can't sign up on its owntawk.to vs Freshdesk