Connection
A managed WhatsApp port for every agent stack.
GatewayPort hosts the session, keeps connection health visible, and exposes WhatsApp context without forcing each team to rebuild the same fragile bridge.
WhatsApp for Agents
GatewayPort hosts the WhatsApp connection, turns messages and media into agent-ready context, and exposes tools that any MCP or API agent can use with human approval.
Agent workspace
MCP tools connectedApproval queue
Human gate activeDraft awaiting approval
Maria, I reviewed the audio and image. Please send the signed PDF so we can finish the setup today.
Hosted layer
The first GatewayPort offer is intentionally simple: we host and monitor the WhatsApp connection inside our own infrastructure, then expose the account through a controlled API and MCP surface. Plans scale by message volume, media processing, storage, and memory.
Connection
GatewayPort hosts the session, keeps connection health visible, and exposes WhatsApp context without forcing each team to rebuild the same fragile bridge.
Media
Plans scale with media volume because transcription, vision, file storage, and memory are the real variable costs behind an agent-ready inbox.
Control
Outbound actions can be gated by approval rules, audit logs, and send limits so WhatsApp does not become an uncontrolled automation channel.
Agent interface
GatewayPort is designed as the bridge between real WhatsApp conversations and agentic systems that need context, files, actions, and limits.
Give agents structured access to contacts, recent messages, unread threads, attachments, and conversation summaries.
Transcribe audio, inspect images, extract document context, and keep the original files linked to the conversation.
Let the agent prepare messages with context, tone, and next steps before a person approves the final send.
Use webhooks, APIs, and MCP tools to connect WhatsApp to CRMs, support desks, Codex, Claude, n8n, or custom internal agents.
Persist preferences, decisions, files, and past interactions so the agent does not start from zero every time.
Keep logs for reads, drafts, approvals, outbound messages, failed sends, and connection events.
How it works
GatewayPort does not try to be the agent. It is the operating layer that gives your agent a reliable WhatsApp surface, rich context, and clear boundaries.
A customer, partner, or team member sends text, audio, image, or a file through WhatsApp.
The hosted session turns the conversation into agent-readable context and processes heavy media when needed.
Codex, Claude, ChatGPT, n8n, or your own agent can call MCP/API tools instead of scraping a phone session.
Drafts, sensitive sends, and automations can wait for approval before anything leaves the WhatsApp account.
Built by operators
GatewayPort packages the connection layer behind that experience so other agents, teams, and tools can safely connect to a user's WhatsApp account.
Roadmap
Private beta
The beta is for builders, agencies, and operators who want their agents to understand WhatsApp without maintaining their own session hosting, media pipeline, and approval layer.