pingwa vs linked-device WhatsApp tools
A wave of WhatsApp integrations for AI agents are built on Baileys, whatsmeow or other QR-scan “linked device” bridges. They set up fast — by linking your WhatsApp account. That is exactly what puts your number at risk.
Side by side
| pingwa | Baileys / whatsmeow / QR-scan tools | |
|---|---|---|
| Transport | Official Meta Cloud API | Reverse-engineered WhatsApp Web protocol |
| Whose number sends | pingwa's own service number | Your personal WhatsApp, linked via QR |
| Ban risk to you | None — you never link your account | High — personal number can be permanently banned |
| Terms of Service | Compliant (sanctioned API) | Violates WhatsApp ToS |
| Setup | Text join, get an API key |
Scan a QR to link a device |
| Uptime | Hosted 24/7 — works on CI, cron, closed laptop | Often needs a live session / your device online |
| Two-way (ask + tap buttons) | Yes, native in one API call | Varies; usually plain text only |
| Recipient | Only your own phone (spam-proof) | Any contact your linked account can reach |
Why the ban risk is real, not theoretical
Widely reported by people running these libraries:
- WhatsApp actively detects and bans accounts using reverse-engineered clients — even low-volume, reply-only usage, not just bulk senders.
- Roughly 1 in 5 accounts on an unofficial WhatsApp API is reported banned within a year.
- An unofficial-API ban is permanent — there is no appeal. Appeals only work if you were on the official API.
- An entire cottage industry of “anti-ban” middleware exists precisely because the bans are so common.
pingwa sidesteps all of this by being on the official Cloud API and never touching your personal account.
pingwa vs built-in agent notifications (Claude Remote Control & Channels)
Claude Code now ships Remote Control — first-party pings and approvals in the Claude app. If that covers you, use it. Its edges are where pingwa lives:
| pingwa | Remote Control / Channels | |
|---|---|---|
| Coverage | Any agent, script, cron or CI — anything that can curl | Claude Code sessions only |
| Auth | A Bearer key — works with any setup | claude.ai OAuth only; API keys not supported |
| Enterprise | Works everywhere, including Bedrock / Vertex users | Blocked on Bedrock/Vertex; off by default on Team/Enterprise |
| Channel | WhatsApp — the app already open in your pocket | Claude app push; Channels preview: Telegram/Discord/iMessage, no WhatsApp |
| Headless (CI, cron, servers) | Yes — plain HTTP, no session needed | Needs a live local Claude Code session |
The honest caveat
The official Cloud API is not magic immunity — any WhatsApp sender has quality tiers and policy rules. The difference is the kind of risk: the official path has warning signals and recovery, and the number at stake is pingwa's, not yours. A linked-device ban hits your personal WhatsApp, instantly and permanently.
Not affiliated with, or a comment on any specific project — Baileys and whatsmeow are named as the common underlying techniques; Claude Code, Remote Control and Channels are Anthropic products, described here as publicly documented (research preview, subject to change). pingwa is an independent, self-hosted service. See about and privacy.