# API-Supp Review A $7.50/month bridge that connects your existing WhatsApp number to Claude, ChatGPT, or your own code via MCP and REST API. ## Editor's Score: 61/100 Ease of use scores well because the cloud MCP path genuinely requires only a URL paste and a QR scan, and the REST API is straightforward bearer-token JSON with no complex setup. Value is reasonable at $7.50/month flat with no per-message fees and a free first month, though the absence of any volume discount hurts teams linking multiple numbers. Capability is limited by the unofficial bridge: no template messages, no Meta-approved broadcast capability, and the file/voice feature is locked to the single-number local MCP mode, putting it behind tools with official API access. Delivery scores in the single digits because the core delivery risk is structural and documented in the product's own description: the unofficial WhatsApp bridge operates outside Meta's Terms of Service, meaning account termination is a real and unmitigated risk for any business use, not a theoretical edge case. ## Pros - Three distinct connection modes (REST API, cloud MCP, local MCP) from a single linked number, with no duplication of setup required. - Cloud MCP requires zero installation: paste one URL into Claude or ChatGPT and the number is immediately accessible to the AI agent. - First month free with no credit card, and $7.50/month flat per number with no per-message fees layered on top. ## Cons - Built on an unofficial WhatsApp bridge rather than Meta's Cloud API, meaning WhatsApp's Terms of Service prohibit most business use cases and Meta can terminate the linked-device session at any time without warning. - Local MCP mode (the only mode that supports file attachments and voice notes) is limited to a single number and requires running an open-source server process on your own computer, adding operational overhead the cloud mode avoids. - No free tier after the trial month, and no volume discount or team pricing visible on the pricing page; a team linking five numbers pays $37.50/month with no reduction. ## Pricing Paid. - Per Number: $7.50 Pricing reflects what we saw at the time of review (2026-11). Confirm current pricing on the official site. Category: AI Agents & Automation (https://aitoolseekers.com/category/ai-agents-automation) Official site: https://api-supp.com/ Last verified by a human: 2026-11-14 Reviewed by a human at AI Tool Seekers, a hand-reviewed AI tools directory. Every listed tool is verified by a person before publishing. Scores are editorial opinions from a fixed rubric (capability, ease of use, value, delivery on promise) and cannot be bought; there is no pay-to-rank. Directory: https://aitoolseekers.com This review: https://aitoolseekers.com/tools/api-supp Methodology: https://aitoolseekers.com/how-verification-works ## Verdict API-Supp is the fastest path for a solo developer who wants to wire a personal or business WhatsApp number into Claude or ChatGPT without touching Meta's official Cloud API. The tradeoff is real: it runs on an unofficial WhatsApp bridge, which means Terms of Service exposure and no Meta-backed uptime guarantees, a gap that tools built on the official API do not have. Teams with compliance requirements or high message volumes should look elsewhere. Best for: Solo developers and indie builders connecting WhatsApp to AI agents Not for: Compliance-sensitive businesses or teams needing Meta-approved API access ## Overview API-Supp (branded on its site as "apisapp") does one focused thing: it links a WhatsApp number you already own to external code or AI assistants by acting as a bridge between WhatsApp's mobile client and an HTTP API. You scan a QR code in WhatsApp's Linked Devices menu, and from that point your number is reachable via a plain JSON REST API, a cloud-hosted MCP server, or a local open-source MCP server you run on your own machine. The three connection modes are genuinely distinct. The REST API suits developers who want to send and receive messages from their own backend or from automation tools like n8n and Make. The cloud MCP option requires nothing beyond pasting a single URL into ChatGPT or Claude, making it the lowest-friction path to a WhatsApp-aware AI agent. The local MCP mode, hosted on GitHub, adds file attachments, voice notes, and media downloads that the cloud mode does not expose, at the cost of running a process on your computer. The critical context a buyer needs: API-Supp is not built on Meta's official WhatsApp Cloud API. It uses an unofficial bridge that keeps your number connected through WhatsApp's Linked Devices feature, the same mechanism WhatsApp Web uses. That means no Meta approval process and no per-message fees from Meta, but it also means the connection operates outside WhatsApp's Terms of Service for business use, and Meta can terminate linked-device sessions without notice. For a developer experimenting or building a personal automation, that tradeoff is often acceptable. For a business sending customer-facing messages at scale, it is a meaningful legal and operational risk. At $7.50 per number per month with a free first month, the price is low enough that the risk calculus is mostly about compliance, not cost. ## Who should use it API-Supp fits a narrow but real audience well: the solo developer or small technical team that wants to add WhatsApp send/receive capability to a side project, internal tool, or AI agent prototype without going through Meta's business verification process. The QR-code setup and the one-link MCP integration mean a working prototype can exist in under an hour, which is genuinely useful for people who want to test an idea before committing to a more formal integration. Anyone running a customer-facing business that depends on WhatsApp for support or sales should look elsewhere. The unofficial bridge creates account-ban risk that a production system cannot absorb. Relaytiv, which is in our directory, is built on compliant omnichannel infrastructure and covers WhatsApp alongside Instagram, Messenger, and web chat; it is the better fit for a business that needs reliability and Terms of Service coverage. Developers who need Meta's official Cloud API with full template message support and per-message billing should go directly through a Meta Business Solution Provider rather than an unofficial bridge. ## FAQ Q: Is this the official WhatsApp Business API from Meta? A: No. API-Supp uses an unofficial bridge based on WhatsApp's Linked Devices feature, the same mechanism WhatsApp Web uses. It is not built on Meta's Cloud API and does not require Meta business verification, but it also operates outside WhatsApp's Terms of Service for business messaging. Q: How much does it cost, and is there a free trial? A: The only plan is $7.50 per WhatsApp number per month. The first month is free with promo code WHATSAPP100, and no credit card is required to start. Q: Can I connect more than one WhatsApp number? A: Yes. Multiple numbers can be added to a single account, each with its own isolated API token. Each number is billed separately at $7.50 per month. Q: What is the difference between the cloud MCP and the local MCP? A: The cloud MCP requires no installation and works with all numbers on your account; you paste one URL into Claude or ChatGPT. The local MCP runs on your own computer, supports only one number, but adds file attachments, voice notes, and media downloads that the cloud mode does not expose. Q: Can I use this with n8n or Make? A: Yes. The REST API is plain JSON over HTTPS and works with any HTTP-capable automation tool, including n8n and Make, as stated on the product's own feature page. Q: What happens to my WhatsApp number if the service goes down? A: Because the connection runs through WhatsApp's Linked Devices feature, your primary WhatsApp account on your phone continues to work normally. However, API calls and webhook delivery would fail until the service recovers, and Meta can also terminate linked-device sessions independently.