Evolution API vs the Official WhatsApp Business API: Costs, Risks and Which to Use for an AI Agent
Updated
You want an AI agent to answer your customers on WhatsApp, and you’ve found two routes: Meta’s official WhatsApp Business API, or Evolution API, an open-source tool that connects a regular number with no per-message fees. Both work, but they differ a lot in cost, risk and what they let you do. Here’s the full comparison, with Meta’s pricing as of October 2026.
The short answer
- The official API (WhatsApp Business Platform / Cloud API) is the route Meta allows and supports. You pay per delivered message and, since 1 October 2026, Meta also charges for replies inside the 24-hour window. It’s the right choice for high-volume customer service, campaigns, notifications and any number your business can’t afford to lose.
- Evolution API connects a regular WhatsApp number through the WhatsApp Web protocol. There’s no per-message fee and the agent can do what a person can (groups, voice notes), but it’s an unofficial route: the number can be banned.
- Business bots are still allowed. What Meta banned from 15 January 2026 are general-purpose AI assistants (ChatGPT-style) on the API, not an agent that serves your company’s customers.
- Rule of thumb: if the channel is business-critical or you’ll message lots of contacts first, go official. For one-to-one conversations at moderate volume, internal use or groups, Evolution API can be the better fit, with a fallback ready.
- It isn’t a forever decision: a well-built agent can switch channels without being rebuilt.
What is the official WhatsApp Business API?
The WhatsApp Business Platform is Meta’s product for connecting businesses to WhatsApp from their own software. Today it runs on the Cloud API, hosted by Meta: your system (or your AI agent) sends and receives messages through API calls, and your customers see them in their usual WhatsApp.
Don’t confuse it with the WhatsApp Business app, the free mobile app for small businesses. The app is built for a person to reply by hand; it doesn’t officially support plugging in an AI agent.
How to get access
- A Meta business portfolio (Meta Business Suite) with a WhatsApp Business account.
- A phone number that isn’t in use on the personal WhatsApp app. If you already use the WhatsApp Business app on that number, some providers can connect it to the API without losing it (Meta calls this “coexistence”), with some limitations.
- A display name approved by Meta.
- Approved templates for any message sent outside the 24-hour window.
- Business verification (recommended): a new portfolio can only start conversations with 250 unique people per 24 hours. Verifying raises that to 2,000, and Meta then scales it automatically if your message quality stays high.
You can go direct with Meta (you’ll need someone technical to set up the app, tokens and webhooks) or through a BSP (Business Solution Provider), a Meta-approved partner that provides the connection and often an inbox and campaign tools. Most BSPs charge a monthly fee, a markup on Meta’s rates, or both.
Templates and the 24-hour window
This is the rule that shapes an AI agent the most:
- When a customer messages you, a 24-hour customer service window opens (it resets with every message they send). Inside it, the agent can reply freely: text, images, audio, documents.
- Outside that window, you can only send an approved template, categorised as marketing, utility (confirmations, order updates) or authentication (one-time codes).
- If the customer arrives from a click-to-WhatsApp ad or your Facebook Page button and you reply within 24 hours, a 72-hour window opens in which every message is free.
In practice: the agent can reply freely while the customer is chatting, but to pick the conversation back up days later (an appointment reminder, a pending quote) you need a template.
How much does the WhatsApp Business API cost?
Meta has charged per delivered message since 1 July 2025 (it used to charge per conversation). The price depends on the category and the recipient’s country. 2026 brought two big changes:
- 1 July 2026: marketing message rates went up in several markets, including Spain and the UK.
- 1 October 2026: Meta started charging for service messages (free-form replies inside the 24-hour window, whether written by a person or a third-party AI agent) and for utility templates sent inside that window, which used to be free. They’re billed at the same rate as utility messages. Several BSPs report that the first 1,000 service messages per number per month remain free; check your Meta billing dashboard.
| Message type | When it’s used | Indicative cost for recipients in Spain (October 2026) |
|---|---|---|
| Marketing (template) | Offers, campaigns, win-back | About €0.06 per message |
| Utility (template) | Confirmations, reminders, order updates | Around €0.015–0.02 |
| Authentication (template) | Verification codes | Around €0.015–0.02 |
| Service (free-form reply in the 24h window) | What your agent says when a customer writes in | Same as utility since 1 October 2026 (previously free) |
| Customer messages | What customers send you | Free |
| 72h window from an ad | Customers arriving from a click-to-WhatsApp ad | Free |
These are approximate. Rates vary by recipient country, Meta publishes the exact figures on its official rate card and can update them each quarter, and your BSP may add its margin. On top of that comes the AI model cost (cents per conversation), which we break down in our guide to how much an AI agent costs.
For a sense of scale: an agent sending around 5,000 replies a month to Spanish numbers through the official API, beyond the free allowance, would pay Meta roughly €80–100 a month for the messages alone. With Evolution API, that line is zero.
What is Evolution API?
Evolution API is an open-source project (Apache 2.0 licence with brand-protection conditions), hugely popular in the n8n community and in Latin America. You install it on your own server (Docker, with PostgreSQL or MySQL and Redis) and it gives you an API to send and receive WhatsApp messages.
Its most common mode connects a regular WhatsApp number as one more linked device, exactly like opening WhatsApp Web by scanning a QR code. Under the hood it uses Baileys, an unofficial library that implements the WhatsApp Web protocol. Evolution API can also connect to Meta’s official Cloud API, so the same installation can serve both routes.
What its WhatsApp Web mode gives you:
- No per-message fee. You pay for the server, not the messages.
- Real groups: read and post in existing groups of any size, as a person would.
- Voice notes, images and documents, with built-in options to transcribe audio with AI.
- No templates and no 24-hour window: you can message whenever you like.
- Ready-made integrations with n8n, Chatwoot, Typebot, Dify and OpenAI, among others.
- Fast setup: scan a QR code and go, with no Meta verification.
Is Evolution API free? The software is. The server, setup, session monitoring and maintenance aren’t.
Evolution API vs WhatsApp Cloud API: comparison table
| Official API (Cloud API) | Evolution API (WhatsApp Web mode) | |
|---|---|---|
| Who allows it | Meta, with official support | Nobody: it isn’t a route Meta permits |
| Per-message cost | Yes, by category (including replies since October 2026) | No |
| Other costs | BSP fee or markup, if you use one | Server and maintenance |
| Setup | Meta portfolio, approved name, templates | Scan a QR code |
| Messaging customers first | Approved templates only | Unrestricted (with ban risk if you overdo it) |
| Groups | Verified official business accounts only; groups the business creates, up to 8 participants | Any group the number belongs to |
| Voice notes | Yes, send and receive | Yes, send and receive |
| Bulk and marketing sends | Yes, with templates and quality-based limits | No: the fastest way to lose the number |
| Risk of a number ban | Low if you follow the policies | Real, with nobody to appeal to |
| Reliability | Meta’s infrastructure | Depends on your server and the session staying connected |
| Best for | High-volume customer service, notifications, campaigns, critical numbers | One-to-one chats at moderate volume, groups, internal use, pilots |
Can you run an AI chatbot on the WhatsApp Business API in 2026?
Yes. In October 2025 Meta added an “AI Providers” section to its WhatsApp Business Platform terms: from 15 January 2026, developers of AI models are barred when the AI assistant is the primary functionality they offer (think ChatGPT or Perplexity inside WhatsApp). Meta decides what falls into that category.
Meta stated publicly that the change doesn’t affect businesses using AI to serve their customers. An agent that answers questions about your products, books appointments, checks orders or screens candidates is a business bot, and it’s still allowed. How those businesses are charged doesn’t change under this policy either.
In the EU the story isn’t over: in June 2026 the European Commission ordered Meta, as an interim measure in an antitrust investigation, to restore access for rival AI assistants. Meta appealed to the EU General Court in August 2026. For a business bot, none of this changes day-to-day operations.
What we’d recommend on either route:
- Keep the agent focused on your business. A bot that answers anything (writing essays, chatting about whatever) edges towards the general-purpose definition, and it also costs more in AI usage.
- Make it say it’s an AI and offer a human handover.
Use cases: which one to choose
- A clinic or salon confirming appointments and answering questions: official API. Reminders go out as cheap utility templates, the number is the one patients know, and it can’t go down.
- An online shop with order updates and campaigns: official API. For marketing it’s the only safe option.
- A recruitment agency managing candidates and posting jobs to groups: Evolution API, because it needs to be in large existing groups, receives lots of voice notes, and the message volume would make every reply a cost.
- Internal alerts for your team (incidents, job reports, notifications): Evolution API on a dedicated number is usually enough.
- A pilot to validate an agent before investing more: Evolution API on a test number, then move to the official API once the use case is proven.
- A business with both needs: use both. An official number for customers and campaigns, and one connected through Evolution API for groups or internal use, with the same agent behind them.
The risks of setting it up on your own
Both routes have traps that the “WhatsApp AI bot in 10 minutes” tutorials skip:
- Your number gets banned. WhatsApp’s terms prohibit accessing the service through automated or unauthorised means, and WhatsApp can suspend the account. On Evolution API’s WhatsApp Web mode there’s nobody to appeal to.
- You lose the number your customers know. If that number is on your website, your invoices and in hundreds of customers’ contacts, a ban isn’t a technical problem: it’s a commercial one. That’s why we recommend a new number dedicated to this. In the end the client decides, but always after we’ve explained the risks.
- Bulk sends that end in a ban. Sending the same offer to hundreds of contacts from an unofficial number is the most common cause of bans. And on the official API, campaigns that draw complaints lower your number’s quality rating and can get your templates paused.
- Sessions that drop silently. A WhatsApp Web session can disconnect after an update, a change on the phone or a server restart. If nobody’s watching, the agent stops replying and you find out when a customer complains.
- Building on an unofficial library. Evolution API and Baileys depend on WhatsApp not changing its protocol. Evolution API’s latest stable release on GitHub dates from December 2025, with the next version still in testing. If the project stalls, you’re left maintaining the code yourself.
- Costs that creep up unnoticed. On the official API, the October 2026 change means every reply has a price; an agent that answers in five short messages what it could say in one multiplies the bill. And some BSP markups can exceed Meta’s own rate.
- GDPR. Chats are full of personal data: names, phone numbers, addresses, sometimes health or candidate information. You have to inform people, keep only what you need, and decide how long and where it’s processed. A poorly secured Evolution API server exposes every conversation and the number’s session. We cover this in our guide to EU data residency for AI models under the GDPR.
Want to know which route fits your case before you put your number at risk? Book a free call.
Why work with a partner who already runs both in production
A team that has deployed both routes knows where they break. They pick the connection by use case rather than habit, use dedicated numbers when the risk calls for it, monitor the session and alert you if it drops, throttle sending, and keep a fallback ready: an official number the agent can switch to if the unofficial one fails, or a planned migration once volume justifies it.
How we do it at Aitomatik
At Aitomatik we use the official API or Evolution API depending on the use case, and sometimes both in the same project.
One example: we’re building a recruitment agent for a domestic staffing agency. We connected their WhatsApp through Evolution API, with no per-message cost: the agent talks to candidates, understands their voice notes and posts job offers to WhatsApp groups. On the official API it couldn’t post to existing groups the agency didn’t create, and every reply would have a cost.
In every agent we build, whatever the channel:
- We save and evaluate every conversation, to catch mistakes and improve the agent with real data.
- We test every change against real conversations before shipping it.
- For European clients, we use models processed in Europe, with zero data retention and no training, plus a backup model from a different provider, also in the EU. International clients aren’t limited to EU models.
- Optional: a dashboard where your team can see conversations and take over a chat when needed.
If you want to understand what sits behind an agent, start with our guide to what an AI agent is. To connect it to your systems we usually use n8n or custom code. And for a real example of automated support, see how we cut human work in customer support by 80%.
Want an AI agent on WhatsApp?
Tell us what kinds of conversations you get, how many, and how important WhatsApp is to your business. We’ll tell you which route fits, what it will cost each month and how to avoid the risks. See our AI-powered customer service service or book a free call.
Frequently asked questions
Is the WhatsApp Business API free? No. Signing up is free, but Meta charges per delivered message by category. Since 1 October 2026 it also charges for replies inside the 24-hour window. Incoming messages, and conversations that start from click-to-WhatsApp ads (for 72 hours), remain free.
Is Evolution API legal? The software is open source and legal. But using it to connect a WhatsApp number through the WhatsApp Web protocol goes against WhatsApp’s terms, and WhatsApp can suspend the account. It isn’t a crime; the risk is losing the number. And as with any route, you must handle chat data in line with the GDPR.
Why is the WhatsApp API so expensive? It usually isn’t the messages themselves: utility and service messages cost a cent or two in Spain, and a few cents in markets like France or Germany. Bills grow with marketing templates (several times more expensive), BSP fees and markups, and agents that split one answer into many messages. Choosing the right categories and a transparent provider keeps it reasonable.
Can I send bulk messages with Evolution API? Technically yes, but it’s the fastest way to get the number banned. For campaigns and messages to many contacts, use the official API with marketing templates and contacts who have opted in.
Has Meta banned chatbots on WhatsApp? Not business chatbots. Since 15 January 2026 it has barred general-purpose AI assistants whose main function is the AI itself, like ChatGPT, from the API. An agent that serves your business’s customers is still allowed.
Can I move from Evolution API to the official API later? Yes. If the agent is properly separated from the channel, switching means changing the messaging layer, not rebuilding the agent. The delicate part is the number: plan the migration, or start with a dedicated number.
Meta pricing and policies reviewed in October 2026; rates can change every quarter. Last reviewed: 15 October 2026.
