API and MCP · Own product
Grapnel for agents
A product that connects a WhatsApp number to an AI agent by QR code: the agent reads chats and groups and replies over MCP or an API, with scoped keys and billing per number.
- R$ 9,90
- per number per month, no per-message fees
- 8 retries
- of each event within 24 hours if the agent's server is down
- 7 days
- of history in the API to catch up on missed messages

The challenge
AI agents can already write, summarize and decide, but they are left out of WhatsApp, where customers and work groups are. Connecting an agent to the number a business already uses usually means running your own infrastructure and worrying about what the agent is allowed to do.
And the agent needs to hear about new messages without losing events when its server is down, and without sending the same message twice when it retries a call.
What I did
- 01Product, positioning and pricing for AI agents
- 02MCP server and HTTP API on the same Grapnel API
- 03Keys with permissions, expiry and revocation
- 04Signed webhooks, with retries and history to recover events
- 05Landing page demonstrating the flow from WhatsApp to the agent
The solution
Grapnel for agents connects the number through WhatsApp's linked-devices QR code and gives the agent an API key with permissions and a validity of 1 to 365 days, revocable at any time. With it, the agent uses the MCP server or the HTTP API to read chats and groups, reply and send PDFs, audio and locations.
Every new message becomes an event signed with HMAC SHA-256 on the agent's server; if it is down, Grapnel retries up to 8 times in 24 hours, and the history stays in the API for 7 days. Pricing is per connected number, not per message: R$ 9.90 a month, R$ 7.00 from two numbers, or R$ 49.00 a year.
Features
Chats and groups
The agent reads one-to-one chats and groups and sums up the day. Reading one-to-one chats needs the chats:read permission.
Text, PDFs, audio and locations
Replies, files, voice notes and addresses sent from the number the business already uses.
Scoped keys
Each key only does what its permissions allow, lasts 1 to 365 days and stops working once revoked.
Signed webhooks
A new message becomes an event on the agent's server, signed with HMAC SHA-256 and retried if it is down.
No duplicate messages
With the same Idempotency-Key, a retried call does not send the message again.
Disconnection alert
If the number drops, the account owner gets an email with the way to reconnect it.
How it was built
MCP and API with one key
The MCP server (Streamable HTTP) and the REST API take the same Bearer key: any MCP client, or any agent that calls HTTP, talks through the same number.
Events that are not lost
Webhooks signed with the customer's secret and retried with growing backoff on 5xx, 408 and 429 errors: up to 8 attempts in 24 hours, with 7 days of history in the API.
Idempotent sends
Sends accept an Idempotency-Key, so an agent that retries after a failure does not duplicate the message.
Clear limits
60 requests per minute per account and least-privilege keys, so the agent only talks to people who expect it.
The whole page
Scroll to move through the page from top to bottom.

More screens

